There are more keydowns that don't constitute user activation #41393 #42337
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
Abhi-Sharma
requested review from
LeoMcA and
estelle
and removed request for
a team
github-actions
bot
added
Content:HTML
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.
The current documentation states that all keydown events count as user activation except the Esc key and browser-reserved shortcut keys.
However, in practice, several additional keys do not trigger user activation in major browsers (Chrome, Firefox), such as CapsLock, NumLock, and other lock/system keys.
This update clarifies that user activation is not triggered by certain non-character or system keys, making the documentation more accurate and aligned with real browser behavior.