21951 2013-05-07 15:20:26 +0000 [CR] pointermove dispatching when button state changes 2014-03-04 05:20:24 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal CR 1 jrossi jrossi art.barstow asirveda public-pointer-events public-pointer-events-bugzilla oldest_to_newest 87334 0 jrossi 2013-05-07 15:20:26 +0000 http://lists.w3.org/Archives/Public/public-pointer-events/2013AprJun/0134.html http://lists.w3.org/Archives/Public/public-pointer-events/2013AprJun/0141.html Per 5/7 WG meeting, we should add a sentence to clarify pointermove doesn't fire for property state changes when another event (e.g. pointerdown or pointerup) has reported that changed state. 101679 1 jrossi 2014-02-28 23:40:31 +0000 Fixed text in the following change: https://dvcs.w3.org/hg/pointerevents/rev/a9862eea23f5 "A user agent MUST fire a pointer event named pointermove when a pointer changes coordinates. Additionally, when a pointer changes button state, pressure, tilt, or contact geometry (e.g. width and height) and the circumstances produce no other pointer events defined in this specification then a user agent MUST fire a pointer event named pointermove." 101817 2 asirveda 2014-03-04 05:20:24 +0000 I would like to point out that there are two related test assertions 5.4 and 5.5 [1] that cannot be tested: 5.4 When a pointer changes button state, the pointermove event must be dispatched. 5.5 When a pointer changes pressure, the pointermove event must be dispatched. These two test assertions cannot be tested using the current test harness and cannot be run manually. Suggest that we drop them. [1] http://www.w3.org/wiki/PointerEvents/TestAssertions#Test_Assertions_for_pointermove_events