- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jul 2016 21:08:55 +0000
- To: public-pointer-events@w3.org
Just to check, this whole discussion is the reason why on Android, with a paired bluetooth mouse and Chrome 53 Dev with enabled PE, I get some "interesting" results, right? https://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-keyboard-mouse-events moving mouse to my test button: `pointerover > pointerenter > mouseover > mouseenter` clicking the mouse button (note the first 6 events, where the pointer is going out before coming back in, effectively): `pointerout > pointerleave > mouseout > mouseleave > pointerover > pointerenter > pointerdown > touchstart > (gotpointercapture) > pointerup > pointerout > pointerleave > (lostpointercapture) > touchend > pointerover > pointerenter > mouseover > mouseenter > pointermove > mousemove > mousedown > focus > mouseup > click` second click (note the first 6 events, where the pointer is going out before coming back in, effectively): `pointerout > pointerleave > mouseout > mouseleave > pointerover > pointerenter > pointerdown > touchstart > (gotpointercapture) > pointerup > pointerout > pointerleave > (lostpointercapture) > touchend > pointerover > pointerenter > mouseover > mouseenter > pointermove > mousemove > mousedown > mouseup > click` move mouse out of button: `pointerout > pointerleave > mouseout > mouseleave > blur` -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/35#issuecomment-231208030 using your GitHub account
Received on Thursday, 7 July 2016 21:09:02 UTC