- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Sep 2021 16:38:58 +0000
- To: public-pointer-events@w3.org
Let me quickly chime in here. The even that is fired by the browser right before rAF callback is not necessary the position of the real event. That is the event that the brower believe is the right repesentative of the input stream at rAF timestamp. As a result browsers are free to do resampling of the coordinations and other attribtues as they wish. Coaleseced events and particularly the last event in the coalesced event list is guaranteed to be the actual events received by the browser with no manipulation. Since most browsers don't do re-sampling based on rAF and what not the effect you see most often is that the last event in the coalesced event list match to the main event in some attributes (such as coordiantes) but that is not guaranteed and shouldn't be what devs expect. Also note that even if browser does no resampling of the fired event it still doesn't mean that the last event in the coalesced event list exactly matches the event itself. As their movementX,Y will certainly be different if there is more than one event in coalesced event. In general as we tried to mention in the spec devs should either look at the coaelsced event stream (and ignore the event itself) or work only with the event itself. Mix and matching these will not yield in any good outcome. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/409#issuecomment-914458398 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 September 2021 16:39:00 UTC