- From: Richard Robinson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Aug 2024 05:21:45 +0000
- To: public-pointer-events@w3.org
rr-codes has just created a new issue for https://github.com/w3c/pointerevents: == Ambiguity of the value of the `button` property for the `click` event == According to the [pointer events spec](https://w3c.github.io/pointerevents/#the-button-property) , 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. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 August 2024 05:21:46 UTC