We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An update to Chrome's treatment of KeyboardEvent (see intent to ship) has broken iron-a11y-keys-behavior's matching logic for the Escape key. This is preventing, for example, Escape from closing paper-dropdown-menu because iron-menu-behavior treats the key as if it were supposed to be the first character of a menu item.
This is affecting Chrome's new Material Design Downloads page as a beta-blocking issue.
A fix has been proposed (not formatted a patch for this repo though).
Open questions:
The text was updated successfully, but these errors were encountered:
FTR, this also prevents Escape from closing dialogs.
Sorry, something went wrong.
Closing, got fixed in #39 & released in v1.1.2
v1.1.2
No branches or pull requests
An update to Chrome's treatment of KeyboardEvent (see intent to ship) has broken iron-a11y-keys-behavior's matching logic for the Escape key. This is preventing, for example, Escape from closing paper-dropdown-menu because iron-menu-behavior treats the key as if it were supposed to be the first character of a menu item.
This is affecting Chrome's new Material Design Downloads page as a beta-blocking issue.
A fix has been proposed (not formatted a patch for this repo though).
Open questions:
The text was updated successfully, but these errors were encountered: