- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 17:09:55 +0000
- To: public-pointer-events@w3.org
BTW I think the state to track this may be slightly more complex. [Process pending pointer capture](https://w3c.github.io/pointerevents/#process-pending-pointer-capture) says: > If the [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) for this pointer is set and is not equal to the [pending pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pending-pointer-capture-target-override), then fire a pointer event named [lostpointercapture](https://w3c.github.io/pointerevents/#dfn-lostpointercapture) at the [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) node. However, if the [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) lost capture because it was removed from the dom we should be dispatching lostpointercapture at the document. One way to do this without adding additional state is in https://w3c.github.io/pointerevents/#implicit-release-of-pointer-capture we could change the [pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pointer-capture-target-override) to the document and the [pending pointer capture target override](https://w3c.github.io/pointerevents/#dfn-pending-pointer-capture-target-override) to null so that the "document" immediately loses pointer capture. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/487#issuecomment-1779709547 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 17:09:57 UTC