Inconsistent ordering of lostpointercapture and pointerout/leave for touch between Edge and Chrome

Issue #8974782 • Assigned to Andrew B.

Details

Author
Ted D.
Created
Sep 19, 2016
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

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:
http://output.jsbin.com/wahawofufe
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 https://github.com/w3c/pointerevents/issues/142](https://github.com/w3c/pointerevents/issues/142)[https://github.com/w3c/pointerevents/issues/142](https://github.com/w3c/pointerevents/issues/142)

Attachments

0 attachments

    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.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in