- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 07 Aug 2014 23:13:14 +0100
- To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>, "public-touchevents@w3.org" <public-touchevents@w3.org>
On 01/08/2014 19:38, Jacob Rossi wrote: > There is no precedence model here--we support both event models side > by side. Pointer fires, then touch, then mouse. For example: > pointerdown, touchstart, mousedown Note that mouse events still > follow the "interlaced" firing described by the pointer events spec > (not the click sequence firing described by touch events). For the curious, I've done some preliminary testing (using the emulator, due to phone update issues) on event sequence for WinPhone 8.1 Update 1/IE11 http://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-touchscreen-events Interesting to compare the sequence of a clean tap on "pure" touch events devices vs IE11's combined touch/pointer events: touchstart > (touchmove)+ > touchend > (mouseenter) > mouseover > mousemove > mousedown > mouseup > click vs mousemove > pointerover > mouseover > pointerenter > mouseenter > pointerdown > touchstart > mousedown > (gotpointercapture) > focus > pointermove > mousemove > pointerup > touchend > mouseup > (lostpointercapture) > pointerout > mouseout > pointerleave > mouseleave > click (there may be a missing touchmove there, due to emulator https://twitter.com/jacobrossi/status/497498391245754370) Other differences that I seem to get are that in the touch event model, as soon as you use more than one finger, no mouse compat events are fired, whereas for pointer events mouse compat events are fired regardless of number of pointers. 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 Thursday, 7 August 2014 22:13:39 UTC