-
Notifications
You must be signed in to change notification settings - Fork 538
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
Remove non-tab elements from TabNav
focus zone
#2367
Merged
iansan5653
merged 6 commits into
main
from
2319-tabnav-should-exclude-buttons-within-tabs-from-the-focus-zone
Sep 23, 2022
Merged
Remove non-tab elements from TabNav
focus zone
#2367
iansan5653
merged 6 commits into
main
from
2319-tabnav-should-exclude-buttons-within-tabs-from-the-focus-zone
Sep 23, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: c8f19ac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
…-focus-zone' of https://github.com/primer/react into 2319-tabnav-should-exclude-buttons-within-tabs-from-the-focus-zone
colebemis
approved these changes
Sep 23, 2022
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.
Looks good 👍
joshblack
approved these changes
Sep 23, 2022
…bs-from-the-focus-zone
iansan5653
deleted the
2319-tabnav-should-exclude-buttons-within-tabs-from-the-focus-zone
branch
September 23, 2022 18:16
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When there are focuseable elements inside
TabNav
(particularly inside theTab
s themselves) they should not be included in the arrow-key navigation. For example, this menu button should be focuseable via Tab, not via arrow keys:This change filters out any elements without the role
tab
from the focus zone. This fixes #2319 - for more context, please see that issue.Merge checklist
[ ] Added/updated documentationTake a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.