[pointerevents] Clarify the event target of `pointermove` if an event listener of the preceding `pointerrawupdate` explicitly release pointer capture (#509)

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

== Clarify the event target of `pointermove` if an event listener of the preceding `pointerrawupdate` explicitly release pointer capture ==
https://w3c.github.io/pointerevents/#the-pointerrawupdate-event
> The target of [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) events might be different from the [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove) events due to the fact that [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove) events might get delayed or coalesced, and the final position of the event which is used for finding the target could be different from its coalesced events.
> 
> In terms of ordering of [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) and [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove), if the user agent received an update from the platform that causes both [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) and [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove) events, then the user agent MUST dispatch the [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) event before the corresponding [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove).
> 
> Other than the target, the concatenation of coalesced events lists of all dispatched [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) events since the last [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove) event is the same as the coalesced events of the next [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove) event in terms of the other event attributes. The attributes of [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate) are mostly the same as [pointermove](https://w3c.github.io/pointerevents/#dfn-pointermove), with the exception of cancelable which MUST be false for [pointerrawupdate](https://w3c.github.io/pointerevents/#dfn-pointerrawupdate).

It seems that these paragraphs imply that the following `pointermove` event target should be considered with the latest capturing state after dispatching `pointerawupdate`, however, it means that the dispatcher in the browsers need to recompute the target. Therefore, I'd like to confirm that how the spec editors thought about this when they wrote.

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


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

Received on Tuesday, 13 August 2024 04:07:38 UTC