27792 2015-01-09 17:12:10 +0000 Ambiguous Text in Device Button State Table 5.1.1.1 2016-03-15 15:43:54 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 msalsbery jrossi msalsbery public-pointer-events rbyers public-pointer-events-bugzilla oldest_to_newest 116966 0 msalsbery 2015-01-09 17:12:10 +0000 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. 116967 1 jrossi 2015-01-09 18:32:17 +0000 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. 125505 2 rbyers 2016-03-15 15:43:54 +0000 This was addressed in https://github.com/w3c/pointerevents/pull/34