User agent behavior that cancels pointers, incomplete/inaccurate explanation for pointercancel in touch-action section

While formulating a response to "[Bug 26809] New: IE11 on Win8.1 fires a 
click event after pointer  has moved when element has touch-event: none" 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26809 I started poking 
around a bit in the text for 
https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-touch-action-css-property 


Two things: the "meat" of my answer to that bug was

"Normally, even with Pointer Events, if you move your touch point too 
much (again, there are a few pixels of wiggle room), it is again 
considered that you're really doing some gesture or scroll behavior - so 
the pointer is cancelled (pointercancel is fired) and it's left up to 
the UA to handle any further movement/interaction."

Unless I'm mistaken, this aspect is not explicitly mentioned in the PE 
spec at the moment? And if I'm right and it isn't, should it?

Also, just before the examples in that section, we have

"...the user agent must fire a pointer event named pointercancel (and 
subsequently a pointerout event) whenever all of the following are true, 
in order to end the stream of events for the pointer:"

But from my testing in IE11 it seems that pointercancel is fired AFTER 
pointerout. There's also pointerleave that's usually being fired, again 
to "end the stream of events for the pointer". I'd suggest removing 
"subsequently" here, and perhaps adding pointerleave as well?

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Monday, 15 September 2014 15:49:57 UTC