Skip to content

fix(overlay): don't dispatch key events to overlays that don't handle them #11810

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

Conversation

crisbeto
Copy link
Member

Currently we dispatch keydown events to the most-recently-opened overlay, however this means that an overlay that doesn't handle keyboard events will end up blocking the events for all the overlays under it. These changes add a check that will skip overlays that don't subscribe to keydown events when determining which overlay to dispatch the event to.

Fixes #11807.

… them

Currently we dispatch keydown events to the most-recently-opened overlay, however this means that an overlay that doesn't handle keyboard events will end up blocking the events for all the overlays under it. These changes add a check that will skip overlays that don't subscribe to keydown events when determining which overlay to dispatch the event to.

Fixes angular#11807.
@crisbeto crisbeto requested a review from jelbourn as a code owner June 16, 2018 09:41
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 16, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Jun 19, 2018
@josephperrott josephperrott merged commit c3fdc32 into angular:master Jun 29, 2018
@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 Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Snackbar blocks dialog close via escape
4 participants