- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 15:41:28 +0000
- To: public-pointer-events@w3.org
flackr has just created a new issue for https://github.com/w3c/pointerevents: == Implicit release of pointer capture on DOM removal doesn't match touch-events == We trigger [implicit release of pointer capture](https://w3c.github.io/pointerevents/#implicit-release-of-pointer-capture) when an element is no longer connected to the DOM: > When the [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) is no longer [connected](https://dom.spec.whatwg.org/#connected) [[DOM](https://w3c.github.io/pointerevents/#bib-dom)], the [pending pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pending-pointer-capture-target-override) and [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) nodes SHOULD be cleared and also a PointerEvent named [lostpointercapture](https://w3c.github.io/pointerevents/#dfn-lostpointercapture) corresponding to the captured pointer SHOULD be fired at the document. It was my understanding that implicit pointer capture was meant to mimic the behavior of touch events. However with touch events we do continue to fire touch events at the implicitly captured removed node: [demo](https://jsbin.com/rejujop/edit?js,output). Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/486 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 15:41:30 UTC