New issue
Advanced search Search tips

Issue 868694 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Bug



Sign in to add a comment

Pointer Lock API: mouse movement "catches" when pointer locked widget overlaps edge of screen

Reported by clane...@gmail.com, Jul 29

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Steps to reproduce the problem:
1. Start Chromium
2. Navigate to the "Pointer lock demo" at https://mdn.github.io/dom-examples/pointer-lock/
3. Move the chromium window so that the pointer lock demo widget is partially off-screen (consider putting it partially off the right side of the screen, as problematic behavior is different depending on which edge of the screen is overlapped, and the problem is simplest to observe in this case)
4. Click on the pointer lock widget to enter pointer lock mode
5. Move the mouse so that the red ball "wraps" (as it normally does) around the sides of the widget several times. If you move it far enough in the right direction, it will "catch" as though the mouse cursor is stopping at the edge of the screen.

What is the expected behavior?
Expected behavior can be observed when the pointer lock demo widget does not overlap the edge of the screen.

Expected behavior is that it the red dot in the pointer lock demo widget will move freely with mouse input, wrapping around the edges of the widget.

What went wrong?
Mouse movement information passed to the client was not correct, causing the program to behave non-nonsensically.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3507.0 (Developer Build) (64-bit)  Channel: n/a
OS Version: Debian Stretch (stable)
Flash Version: 

Thank you for your attention to this issue. You are wonderful.
 
Labels: Needs-Triage-M70
Cc: viswa.karala@chromium.org
Components: Blink>Input>PointerLock
Labels: Triaged-ET Target-70 M-70 FoundIn-70 OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on chrome reported version# 70.0.3507.0 using Ubuntu 14.04 and Windows-10 with URL provide in comment# 0. As this issue is seen from M-60(60.0.3112.0), hence considering this issue as Non-Regression and marking it as Untriaged.
Note: Tentatively adding Blink>Input>PointerLock components to the issue and issue is not seen on Mac 10.12.6.

Thanks!

Cc: eirage@chromium.org
Status: Available (was: Untriaged)
I can see the issue as well. The position of the window is most likely interfering with Chrome mechanism for reseting the mouse position to the middle of the widget. Ella is that correct? Can we change the reset coordinates to the middle of the visible area of the window?
Cc: -eirage@chromium.org
Labels: -Pri-2 Pri-3
Owner: eirage@chromium.org
Status: Assigned (was: Available)
Yea, looks like it's because the size we are using is partially out of screen. But I'm not sure if we can get the size for visible area instead.
I'll take a look later :)

Sign in to add a comment