W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2015

Compatibility mouse events, take 2?

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Tue, 31 Mar 2015 15:51:50 +0100
Message-ID: <551AB486.40402@splintered.co.uk>
To: public-pointer-events@w3.org
Just wondering, now that Pointer Events just through W3C Rec, if 
isn't at risk now of already being obsolete, since it only reflects 
current IE 11's implementation, and since Microsoft's Spartan is already 
going for a different event order which is more compatible with the way 
mouse events are dispatched in Touch Events?

pointerover > pointerenter > pointerdown > touchstart > focus > 
(gotpointercapture) > pointermove > pointerup > touchend > 
(lostpointercapture) > mouseover > mouseenter > mousemove > mousedown > 
mouseup > click > pointerout > pointerleave

(see last few rows in 

Or is this event order in Spartan only going to come into effect based 
on heuristics (if it's detected somehow that the page, or one of its 
components, registers touch* handlers).

Should there be a clarifying note of sorts? Is this something that needs 
to wait for PE version 2?

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 Tuesday, 31 March 2015 14:52:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 March 2015 14:52:17 UTC