- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2023 21:37:37 +0000
- To: public-pointer-events@w3.org
While reviewing the [fix](https://chromium-review.googlesource.com/c/chromium/src/+/4955773/) @mustaqahmed is working on, I also discovered that when we remove nodes during the dispatch of boundary events we still send events to the removed nodes. E.g. load https://jsbin.com/rawogov/edit?html,css,js,output and move the mouse from the blue box up. The green removed box still gets an event. I think this is also in violation of the [ui-events section](https://w3c.github.io/uievents/#events-mouseevent-event-order:~:text=If%20the%20event%20target%20(e.g.%20the%20target%20element)%20is%20removed%20from%20the%20DOM%20during%20the%20mouse%20events%20sequence%2C%20the%20remaining%20events%20of%20the%20sequence%20MUST%20NOT%20be%20fired%20on%20that%20element.) which states: > If the [event target](https://w3c.github.io/uievents/#event-target) (e.g. the target element) is removed from the DOM during the mouse events sequence, the remaining events of the sequence MUST NOT be fired on that element. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/477#issuecomment-1804722538 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 November 2023 21:37:39 UTC