- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Jan 2017 15:48:27 +0000
- To: public-pointer-events@w3.org
Here's a [chromium bug](https://bugs.chromium.org/p/chromium/issues/detail?id=678258). 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 PointerLock](https://w3c.github.io/pointerlock/#extensions-to-the-mouseevent-interface) 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 practice. 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 https://github.com/w3c/pointerevents/issues/131#issuecomment-270403820 using your GitHub account
Received on Wednesday, 4 January 2017 15:48:32 UTC