-
-
Notifications
You must be signed in to change notification settings - Fork 78.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allows tab function to be used with OL and UL #26650
Conversation
There are times when an `<ol>` is the correct node to use for a list, but the current tab() function will only work with either `<ul>` or `<nav>`. This PR changes `ACTIVE_UL` to `ACTIVE_LIST` and adds `nodeName === 'OL'` to the two checks for the tab button's parent node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a unit test which cover this case
Actually curious to know how the current unit tests pass (assuming |
I think you're right but can you add or change a unit test with a valid example ? |
Sure. Won't be today, but I'll try to add something within a day or two. |
@Johann-S Should the |
Adds OL versions of visual tests and unit tests, with some tweaks to visual tests to indicate which use UL and which use OL.
No we made the decision to remove in our vendors because it's in our dev deps, so you have to install it with NPM, and please do not commit dist files |
Okay, it'd probably be easiest if I close this, delete my fork, and create a new one with just the required updates. Is patch-2 the correct branch to be working from? |
you can call your branch whatever you want 😉 |
There are times when an
<ol>
is the correct node to use for a list, but the current tab() function will only work with either<ul>
or<nav>
.This PR changes
ACTIVE_UL
toACTIVE_LIST
and addsnodeName === 'OL'
to the two checks for the tab button's parent node.