- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 May 2021 14:56:57 +0000
- To: public-pointer-events@w3.org
Regarding the `coalesced event list` it was intentional. As pointerrawupdate might also be delayed (not due to the rAF) but due to the main thread being busy running js code. So potentially they could also get coalesced. Regarding the prediction we didn't see much of a need for that at the time based on the use cases. That was the reasion behind this at the time of writing the spec. Note that we can always go back and add prediction list as well to `pointerrawupdate` if the need rises. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/380#issuecomment-851543496 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 May 2021 14:57:02 UTC