This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27792 - Ambiguous Text in Device Button State Table 5.1.1.1
Summary: Ambiguous Text in Device Button State Table 5.1.1.1
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-09 17:12 UTC by Mark Salsbery
Modified: 2016-03-15 15:43 UTC (History)
3 users (show)

See Also:

Attachments

Description Mark Salsbery 2015-01-09 17:12:10 UTC 
In the "Device Button State" table in section 5.1.1.1, perhaps the text should be something like "Mouse move with no button state change" instead of "Mouse move with no buttons pressed".

This would match the current IE 11 implementation where pointermove events have a button value of -1 when the mouse pointer moves with button(s) pressed.

The current text could be misinterpreted by other vendors implementing the pointer events model causing incompatibilities.
Comment 1 Jacob Rossi [MSFT] 2015-01-09 18:32:17 UTC 
Hmm, I can see how that might clarify the button property a bit more. But then it would cause similar confusion for buttons, which only has a value of 0 when no buttons are pressed (not just when no buttons have changed). 

Given we link to the more detailed definitions of theses properties in D3E, several browsers already implement these properties, and that we have extensive test cases for this, I think we can live with this one (avoiding a change to the spec as it's about to go to REC). I don't think there's a real risk of implementers shipping the wrong thing.
Comment 2 Rick Byers 2016-03-15 15:43:54 UTC 
This was addressed in https://github.com/w3c/pointerevents/pull/34