Skip to content
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

Ambiguity of the value of the button property for the click event #513

Open
rr-codes opened this issue Aug 16, 2024 · 0 comments
Open

Ambiguity of the value of the button property for the click event #513

rr-codes opened this issue Aug 16, 2024 · 0 comments

Comments

@rr-codes
Copy link

According to the pointer events spec , a pointer event should have a button value of -1 if "Neither buttons nor touch/pen contact changed since last event".

However, this is inconsistent with the behavior of when the click event was a MouseEvent, where the button property would return 0 (for the primary button).

Additionally, it says

The click event should only be fired for the primary pointer button (i.e., when button value is 0, buttonsvalue is 1)

which further seems to contradict the statement that button should be -1 if it hasn't changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant