[pointerevents] Clarify `pointermove` event (or following event of pointer boundary events) target if preceding pointer boundary event listener removes the `pointerover` target (#536)

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

== Clarify `pointermove` event (or following event of pointer boundary events) target if preceding pointer boundary event listener removes the `pointerover` target ==
[The `mousemove` vs. `mouseover` issue is here.](https://github.com/w3c/uievents/issues/393)

If `pointerover` event target is removed by an event listener, where the source event should be targeted?

According to [the test results](https://wpt.fyi/results/pointerevents/pointermove_after_pointerover_target_removed.tentative.html?label=experimental&label=master&aligned), nobody dispatches `pointermove` to the closest connected ancestor of the removed `pointerover` target.

This means all browsers compatible unless they may dispatch `pointermove` to the root element, the `Document` node or the `Window`. However, I'm not sure whether this is useful behavior for web developers.

Once we align the behavior of `mousemove` in the above issue, aligning Pointer Events behavior to it may be reasonable.


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


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

Received on Wednesday, 5 February 2025 09:05:47 UTC