Move layerX/layerY from UIEvent to MouseEvent #16267
Merged
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
These are non-standard properties, but if they are standardized it will be on MouseEvent, see w3c/uievents#135. Furthermore, it's only on MouseEvent that these properties ever return something other than zero. The apparent removal in Chrome 45 was caused by the move from UIEvent to MouseEvent in Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=503276 Since MouseEvent inherits from UIEvent, we can ignore this prototype move in BCD, per our guidelines: https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines.md#apis-moved-on-the-prototype-chain
github-actions
bot
added
the
data:api 🐇
teoli2003
added
the
needs content update 📝
|
We have these two pages on mdn/content that needs to be adapted/removed: https://developer.mozilla.org/en-US/docs/Web/API/UIEvent/layerX Setting the Needs content update label. |
queengooborg
approved these changes
May 13, 2022
|
Content update sent in mdn/content#15993. |
sideshowbarker
approved these changes
May 13, 2022
queengooborg
removed
the
needs content update 📝
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These are non-standard properties, but if they are standardized it will
be on MouseEvent, see w3c/uievents#135.
Furthermore, it's only on MouseEvent that these properties ever return
something other than zero.
The apparent removal in Chrome 45 was caused by the move from UIEvent to
MouseEvent in Chromium:
https://bugs.chromium.org/p/chromium/issues/detail?id=503276
Since MouseEvent inherits from UIEvent, we can ignore this prototype
move in BCD, per our guidelines:
https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines.md#apis-moved-on-the-prototype-chain