-
-
Notifications
You must be signed in to change notification settings - Fork 637
Update to ARIA 1.2; fix test failures #696
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
Conversation
@@ -192,7 +192,6 @@ const alwaysValid = [ | |||
{ code: '<div role="presentation" />' }, | |||
{ code: '<div role="region" />' }, | |||
{ code: '<div role="rowgroup" />' }, | |||
{ code: '<div role="scrollbar" />' }, |
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.
is this a breaking change? or would you consider it a bugfix?
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.
@ljharb Breaking change in behavior, but not API. This will be a Minor release. Some new violations will probably pop up for folks when they run their linter. Does this sound right?
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.
semver for eslint rules is tricky; “more errors” is definitely at least a minor, but the real question is whether they have a reasonable expectation that the code shouldn’t be warned on. If this code getting a new warning will help them catch a bug instead of surprising them, then that seems nonmajor?
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.
If this code getting a new warning will help them catch a bug instead of surprising them, then that seems nonmajor?
Thinking on this more, Authors will most likely be removing overrides put in place because scrollbar wasn't considered an interactive element before now, so putting a click handler on one would have raised a lint warning. That'll be good to note in the release notes.
1fa93d8
to
f87561d
Compare
In testing the ARIA 1.2 upgrade in I found one instance of I found one instance of And, And, And, Errors/Warnings were virtually the same over 120,000 files. I'm confident in this upgrade. |
woot, ship it (once tests pass) |
See aria-query's update to ARIA 1.2: A11yance/aria-query#46
The changes
scrollbar
becomes an interactive elementslider
andspinbutton
lose some required propsaria-selected
,aria-expanded
,aria-invalid
andaria-haspopup
are no longer allowed on several roles.