[pointerevents] Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target (#623)

masayuki-nakano has just created a new issue for https://github.com/w3c/pointerevents:

== Clarify `mousemove` event target if preceding `mouseout`, `mouseleave`, `mouseover` or `mouseenter` event listener removes the `mouseover` target ==
For example if website does:

```js
foo.addEventListener("mouseover", event => event.target.remove());
```

Then, where `mousemove` event should be targeted?

Firefox started targeting the closest connected ancestor of the removed target since 135.0.1 or later (not yet fixed the schedule, see [bug 1944191](https://bugzilla.mozilla.org/show_bug.cgi?id=1944191). Before that, Firefox dispatched `mousemove` event on the `Document` node.

Chrome does same thing if enabling the new experimental behavior of mouse/pointer boundary events. However, Chrome with disabling the feature dispatches `mousemove` on the removed target.

According to [the test result](https://wpt.fyi/results/uievents/mouse/mousemove_after_mouseover_target_removed.html?label=experimental&label=master&aligned), Safari does not dispatch `mousemove` event or dispatches on the root element or dispatching to the `Document` or the `Window`.

Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/623 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 January 2026 22:04:40 UTC