[pointerevents] Need to clarify click event firing for chorded buttons?

mustaqahmed has just created a new issue for 
https://github.com/w3c/pointerevents:

== Need to clarify click event firing for chorded buttons? ==
The UI Event Spec 
[says](https://www.w3.org/TR/DOM-Level-3-Events/#event-type-click):
> The click event should only be fired for the primary pointer button 
(i.e., when MouseEvent.button value is 0, MouseEvent.buttons value is 
1). Secondary buttons (like the middle or right button on a standard 
mouse) must not fire click events.

We need to clarify what it means for chorded buttons. For example, 
should we fire a click in any of these sequences?

1. L-button-down (=> pointerdown),
  M-button-down (=> pointermove),
  L-button-up (=> pointermove),
  M-button-up (=> pointerup).

2. M-button-down (=> pointerdown),
  L-button-down (=> pointermove),
  L-button-up (=> pointermove),
  M-button-up (=> pointerup).

The spec is not clear here. If we agree that none of the above 
sequences fire clicks, then the spec can say:
> A click is fired only for a "pointerdown with <code>button=0</code>"
 followed by a "pointerup with <code>button=0</code>".

Otherwise, it can define click to be a function of primary button 
activity:
> A click is fired for a "pointerdown/pointermove with 
<code>button=0</code> that sets the LSB of <code>buttons</code>" 
followed by a "pointerup/pointermove with <code>button=0</code> that 
resets the LSB of <code>buttons</code>".


Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/93 using your GitHub 
account

Received on Tuesday, 21 June 2016 15:40:48 UTC