.screenX and .screenY are different for "mousemove" and "wheel" events while pointer lock is on
Reported by
henn...@still-hidden.de,
Mar 9 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. In the test case, move the mouse, scroll and compare the screenX/screenY of the events in the console 2. Click to enable pointer lock 3. Move and scroll again, screenX/screenY are different this time. The ones of "mousemove" are always the same. What is the expected behavior? screenX/screenY to be the same What went wrong? screenX/screenY are different Did this work before? N/A Does this work in other browsers? No Opera has the same issue, no bug filed yet. Firefox doesn't. Chrome version: 56.0.2924.87 Channel: stable OS Version: Arch Flash Version:
,
Mar 9 2017
,
Mar 9 2017
,
Mar 14 2017
The actual problem is that wheel events when pointer lock is on aren't re-targeted to the pointer lock target. The spec clearly indicates that wheel events should be re-targeted.
,
Mar 14 2017
nzolghadr@ Navid I examined this and it will likely need more surgery to the code than I anticipated. We can probably block this on your unification of the pointer lock, event target code no?
,
Mar 14 2017
I agree with you.
,
Jan 7
Assigning this to Ella as she is now the owner in that space. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by henn...@still-hidden.de
, Mar 9 2017501 bytes
501 bytes View Download