Merge KeyboardEvent/MouseEvent.which into UIEvent.which #8751
Conversation
This file contains 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
Preview URLsFlawsNone! 🎉 External URLsURL: No new external URLs (this comment was updated 2021-09-08 11:48:01.964348) |
teoli2003
approved these changes
Sep 8, 2021
3 tasks
hamishwillee
pushed a commit
that referenced
this pull request
Jan 2, 2022
The "which" property has been moved into `UIEvent` by #8751.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR folds both the
KeyboardEvent.whichandMouseEvent.whichfeatures into a page forUIEvent.which, followed by their removal. This corresponds with their removal and fusion in BCD (see mdn/browser-compat-data#12185).