Re: [pointerevents] Ambiguity of the value of the `button` property for the `click` event (#513)

Thanks for the catch!  The "since last event" part was added way before `click` was a PointerEvent!!

Possible ways forwards for the spec:
1. Add a special case for `click.button`.  We already have a special case for `click.target` after a released pointer, so should be fine?
2. Change `click.button` to be `-1` because this field is redundant with the `auxclick` event for non-primary buttons.  This would be a breaking change IMO.

-- 
GitHub Notification of comment by mustaqahmed
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/513#issuecomment-2402572037 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 October 2024 14:54:13 UTC