Re: [pointerevents] Support hovering button states

In our call today @scottgonzalez argued that the simplest thing is to 
treat stylus like mouse - send `pointerdown` / `pointerup` on hovering
 button press.  We'd update the spec for this by removing the "pen 
contact" conditions in [chorded button 
interactions](https://w3c.github.io/pointerevents/#chorded-button-interactions).
  Some devices / OSes may not support such hovering button presses, 
and that's fine.

Alternate proposal is to just send `pointermove` with changed 
`buttons` value.  This requires more spec special cases - eg. to allow
 non-active pointers with non-zero `buttons`, redefine "active buttons
 state", etc.

The key difference is in the behavior of naive applications (eg. those
 changing UI just on `pointerdown` events without consulting the 
`button`/`buttons` values).



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

Received on Wednesday, 1 June 2016 15:59:24 UTC