-
-
Notifications
You must be signed in to change notification settings - Fork 32.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
[Tabs] Implement keyboard navigation #20781
Conversation
@material-ui/core: parsed: +0.13% , gzip: +0.15% Details of bundle changes.Comparing: a9f1857...2d12efa Details of page changes
|
@@ -116,6 +116,10 @@ module.exports = { | |||
// does not work with wildcard imports. Mistakes will throw at runtime anyway | |||
'import/named': 'off', | |||
|
|||
// upgraded level from recommended |
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.
Fixed from #20226
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.
We can discuss there what we prefer as a default for v5.
I was wondering about it before reading your comment. I think that if we could start with a benchmark, it would be awesome.
Implements keyboard navigation without "selection-follows-focus" following https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel. This reduces the potential of a breaking change (before tab navigation would not activate either). We only change navigation direction for horizontal tabs in right-to-left-themes following https://material.io/design/usability/bidirectionality.html#mirroring-elements
Preview: https://deploy-preview-20781--material-ui.netlify.app/components/tabs/#simple-tabs
Part of #6955
future work