Re: [pointerevents] Interop: major browsers fire click/auxclick events differently for chorded buttons (#530)

One important point is that any click-like event fired before the very last button-up action has no corresponding `pointerup` event.  This is because any button-change between the very first button-down and the very last button-up becomes a `pointermove` event (even though it still fires a `mousedown` or `mouseup` event), as per [Sec 4.1.1.1](https://w3c.github.io/pointerevents/#chorded-button-interactions).

So the spec needs to clarify that a click does not always have a `pointerdown/up` pair, regardless of which path we take for this issue (whether we fire a click-like event for the first button-release or for every button release).


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


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

Received on Thursday, 5 December 2024 18:44:30 UTC