Steps to reproduce
Current Chrome (55.0.2865.0): pointerup lostpointercapture pointerout pointerleave
Edge: pointerup pointerout pointerleave lostpointercapture
Spec (and tests) should say which it should be.
One benefit of the Chrome model is that it’s consistent with what web developers would expect for a hovering pointer (like mouse).
Just to add when using button like in this example:
Edge does generate the same order of the events as Chrome. However in this example which the element is div what Rick said happens.
http://output.jsbin.com/fiyoqokEdge has probably always done it this way for touch, so that in theory could be more web compatible.
GitHub URL: https://github.com/w3c/pointerevents/issues/142
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Assigned To to “Sermet I.”
Changed Assigned To from “Sermet I.” to “Andrew B.”