- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Apr 2021 22:32:32 +0000
- To: public-pointer-events@w3.org
patrickhlauke has just created a new issue for https://github.com/w3c/pointerevents: == Clarify what the coalesced/predicted targets dirty stuff is actually about == It's currently a bit implicit (and probably not made super clear by the language we use), but my layperson's understanding is: it can happen that during a movement of the pointer, the pointer moves over various different targets. so in the case of the non-coalesced/raw events inside the coalesced event list, and the predicted events in the predicted event list, it can happen that those individual events belong/point to different targets. *but* when the `getCoalescedEvents` and `getPredictedEvents` methods are called, this gets sanitised so that even though the pointers were above different targets, they are all made to appear as if they were on the original target of the `pointermove`/`pointerrawmove` event that the method was called on. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/370 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 April 2021 22:32:34 UTC