Skip to content

fix(cdk/a11y): not restoring focus to elements inside the shadow DOM #22622

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

Merged
merged 1 commit into from
May 7, 2021

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 3, 2021

The focus trap directive has the ability to restore focus to the previously-focused element on destroy automatically, however the logic doesn't account for the fact that document.activeElement will point to the shadow root if the element is inside the shadow DOM.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent Accessibility This issue is related to accessibility (a11y) target: patch This PR is targeted for the next patch release labels May 3, 2021
@crisbeto crisbeto requested review from mmalerba and annieyw May 3, 2021 19:11
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 3, 2021
The focus trap directive has the ability to restore focus to the previously-focused element on destroy automatically, however the logic doesn't account for the fact that `document.activeElement` will point to the shadow root if the element is inside the shadow DOM.
@crisbeto crisbeto force-pushed the focus-trap-shadow-dom branch from 0b74ca7 to fe48751 Compare May 3, 2021 19:24
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I chatted with @crisbeto about cases where multiple shadow DOM roots are nested. The plan is to revisit this (as we handle shadow DOM in other places too).

I guess having a shared function for getting the active element might be reasonable.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label May 3, 2021
@mmalerba mmalerba merged commit 706fc48 into angular:master May 7, 2021
mmalerba pushed a commit that referenced this pull request May 7, 2021
…22622)

The focus trap directive has the ability to restore focus to the previously-focused element on destroy automatically, however the logic doesn't account for the fact that `document.activeElement` will point to the shadow root if the element is inside the shadow DOM.

(cherry picked from commit 706fc48)
mmalerba pushed a commit that referenced this pull request May 7, 2021
…22622)

The focus trap directive has the ability to restore focus to the previously-focused element on destroy automatically, however the logic doesn't account for the fact that `document.activeElement` will point to the shadow root if the element is inside the shadow DOM.

(cherry picked from commit 706fc48)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants