Re: [pointerevents] Clarify whether touch contact must fire a `pointerrawupdate` event (#373)

Yeah I also agree that this seems to be a bug in Chrome. The idea of `pointercancel` was to stop the events in that stream no matter the event type. You seem to be relying on a behavior that is not spec'ed and is a quirk only in Chrome for your usecase. @liviutinta FYI 

As you mentioned I don't think you are using `pointerrawupdate` for that. The intention of that event was solely performance and getting the events to the apps faster than they can render on the screen for say off-screen canvas drawing or cloud gaming that they send the events to the network and whatnot. 

But going back to your use case, we have heard feedbacks for this usecase that people still wanting to react to the input while scrolling. Could you elaborate more on that to see what kind of interaction you want to implement during scroll that is not possible say with scroll-linked animations and whatever new features those folks are working towards these days?


-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/373#issuecomment-839802002 using your GitHub account


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

Received on Wednesday, 12 May 2021 14:07:07 UTC