fix(cdk/a11y): add Shadow DOM support to FocusTrap #32450
Conversation
This file contains hidden or 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
Mr-KRAMA
requested review from
mmalerba and
ok7sai
and removed request for
a team
Mr-KRAMA
force-pushed
the
fix/focus-trap-shadow-dom-clean
branch
from
bff7492 to
eb7960a
Compare
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
FocusTrap wasn't picking up elements inside Shadow DOM, so trapping didn’t work with custom elements.
Added Shadow DOM traversal for first/last tabbable checks and added tests.
Everything passes and works fine. No breaking changes.