You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be a de facto standard for how the back and forward button of mice are mapped to the MouseEvent.buttons field. I would appreciate it if this could be made de jure to avoid future bugs and confusion.
It is nicely specified for MouseEvent.button. But unfortunately, you cannot blindly assume what that means for MouseEvent.buttons as the two attributes already use a differing ordering of buttons.
The text was updated successfully, but these errors were encountered:
I think it makes sense to drop the buttons definition in the UI Event spec. Note that during TPAC this year, there was an agreement that the PointerEvent spec should become the right place for MouseEvent details (see "TOPIC: UI events" in the meeting notes).
There appears to be a de facto standard for how the back and forward button of mice are mapped to the
MouseEvent.buttons
field. I would appreciate it if this could be made de jure to avoid future bugs and confusion.It is nicely specified for
MouseEvent.button
. But unfortunately, you cannot blindly assume what that means forMouseEvent.buttons
as the two attributes already use a differing ordering of buttons.The text was updated successfully, but these errors were encountered: