Add new Tabs option to enable tab navigation to non-active tabs #6802
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.
Fixes #6759
Note that current behavior follows the W3 guidance for the tabs pattern, so we should consider closing out the filed issue without making any fixes or adding any features. At a minimum, I think the default behavior should follow the guidance, possibly with an opt-in option to add this additional tab navigation pattern to use as consumers of the Tabs component feels is appropriate.
Ex one use case for this is if the usage of the
Tabs
component, for whatever reason, feels or looks more like a button group, and users expect to be able to tab to all tabs.Checklist
Can consider tests pending decision to support or not
Changes proposed in this pull request:
enableTabbedNavigation
to theTabs
component, which allows using the tab key to access non-active tabsReviewers should focus on:
insertNonActiveTabsInTabOrder
andaddNonActiveTabsToTabOrder
Screenshot