Re: [pointerevents] Incorrect movementX/Y in PointerEvents

Here's a [chromium 
We plan to just ensure PointerEvent instances for pointerType=mouse 
have their movement values equal to those reported via mouse events, 
while (for now) remaining 0 for the other (absolute) input devices.

It seems to me like we should eventually apply [the algorithm from 
 to the other input devices too - reporting movement as the change in 
screen position between events (and 0 when there has been a break in 
the event stream such as due to an up or leave event).  But I'm not 
sure if this is worth doing - seems unlikely to matter much in 

I guess if we imagine a game that's really designed for mouse where 
moving the mouse around moves your viewing angle, then we would 
probably want dragging a stylus or touch to (by default) also change 
the viewing angle, right?

GitHub Notification of comment by RByers
Please view or discuss this issue at
 using your GitHub account

Received on Wednesday, 4 January 2017 15:48:32 UTC