Clarify the event target of pointermove if an event listener of the preceding pointerrawupdate explicitly release pointer capture

[masayuki-nakano]

https://w3c.github.io/pointerevents/#the-pointerrawupdate-event

The target of pointerrawupdate events might be different from the pointermove events due to the fact that 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 and pointermove, if the user agent received an update from the platform that causes both pointerrawupdate and pointermove events, then the user agent MUST dispatch the pointerrawupdate event before the corresponding pointermove.

Other than the target, the concatenation of coalesced events lists of all dispatched pointerrawupdate events since the last pointermove event is the same as the coalesced events of the next pointermove event in terms of the other event attributes. The attributes of pointerrawupdate are mostly the same as pointermove, with the exception of cancelable which MUST be false for 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.

[smaug----]

The target can be different, isn't " final position of the event which is used for finding the target could be different from its coalesced events" quite clear. And that also basically says that one needs to do anew hit-testing, or otherwise recompute the target.

@masayuki-nakano do you think there is something to clarify here?

[masayuki-nakano]

Okay, then, there should be a test to check it.