-
Notifications
You must be signed in to change notification settings - Fork 45.9k
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
[react-interactions] Repurpose React a11y modules #16997
Merged
Merged
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
Details of bundled changes.Comparing: f6efb22...8a3cb13 react-interactions
|
threepointone
approved these changes
Oct 3, 2019
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.
Spotted a couple of typos, and assumed the rest of the code is just moving/renaming stuff. lgtm.
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.
This PR mostly just re-labels and re-purposes some of the accessibility modules and the components in them. It comes from internal feedback that some of the names were confusing and some of the components felt misaligned for their real main benefit. Notably: folks only cared for using the
FocusManager
component for handling focus containment, and didn't see what it really had to do with managing focus other that that. Based all this feedback, the following changes have been made:FocusManager
->FocusContain
FocusContain
component now only handles containment, and requires a scope be passed to the component viatabScope
. The documentation has been updated to also reflect this.FocusControl
->FocusManager
as people mentioned that the set of functions from this module are essentially management helpers. The docs have also been updated to reflect this.FocusList
->FocusGroup