[pointerevents] Define a low latency event that isn't occur in the document lifecycle

dtapuska has just created a new issue for https://github.com/w3c/pointerevents:

== Define a low latency event that isn't occur in the document lifecycle ==
Chrome has experimented in shipping events relative to rAF. pointermove is only sent once for every rAF callback and occurs just before the rAF callback. Specifically this was done for touch in Chrome 59 and mouse in Chrome 60. See some discussion here #9.

With pointerevent dispatched at rAF time it is useful for some apps that don't produce any in the normal document lifecycle (see issue whatwg/html#2659) to have input right away.

I was wondering if it we should add a pointermove-raw event to enable the cases when pointer moves with low latency are needed. We want to ensure that this isn't the typical usage as the raw events can occur at a much higher frequency (eg. 1000Hz) so I don't think we want to use the same event type as that would conflate the problem. 

Talking with @RByers we discussed that this event shouldn't bubble and is non-cancelable.



Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/214 using your GitHub account

Received on Tuesday, 1 August 2017 20:03:44 UTC