-
Notifications
You must be signed in to change notification settings - Fork 28
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
MouseEvent.layerX/layerY #37
Labels
compat-bug-proposal
Proposals for web compat bugs
Milestone
Comments
Closed
Per #39 (comment) we're not including this in Interop 2022, due to the lack or spec and tests. However, convergence on this is a good idea. The group needs to decide if we're going to track that work as part of Interop 2022 or not. Regardless, next steps seem to be responding to w3c/uievents#135 (comment). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The
MouseEvent.layerX
andlayerY
properties are implemented everywhere but right now they're not interoperable and cause compat pain.Right now, they depend on internal layerization details in WebKit and Blink (which are different and subject to change). Gecko's definition is somewhat reasonable but of course doesn't match those.
Bug reports
webcompat/web-bugs#94500 is a fairly-recent one.
Specification
None (that's the problem!) but I have a reasonable (I think) proposal here.
Tests
None (also a problem!) but I'm happy to write some if we agree on a definition.
This is a bug to include in #9
Note that I wasn't sure this was suitable for the compat-2022 effort because of the lack of spec right now, but I think it's a relatively minor feature such as that it shouldn't be hard to come up with a proper spec during the next months.
The text was updated successfully, but these errors were encountered: