1607852 - Press TAB to view leaderboard on Tanki Online, and then release TAB, somethings it requires a user gesture to make pointerLock working

Status: RESOLVED DUPLICATE of bug 1944580

(Core :: DOM: Core & HTML, defect, P3)

Description

[u652361]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

For example, if I play Tanki Online, when I press TAB to view leaderboard, and then release TAB, my cursor doesn't focus in game again. (Or Pause menu instead of Leaderboard, same thing)

Actual results:

The cursor didn't focus and I had to click again for it to focus.

Expected results:

It should focus on the game automatically as in Google Chrome.

Comment 1

[Alexandra Martin]

Hi,

Thank you for submitting the report. I was able to reproduce the issue on Win10x64 and Mac 10.14 using Firefox versions 72.0.1, 73.0b4 and 74.0a1 (2020-01-12). I am assigning a component to get an opinion from the development team.

Comment 2

[u652361]

There is also another issue. Scrolling Bars. They are not "designer", I want to say, on Google Chrome for example, they are (CSS or what probably), but CSS doesn't affect those in Firefox. And scrolling is very very slow when you use the scroller on your mouse. On Chrome, it seems to be normal.

Comment 3

[Edgar Chen [:edgar]]

(In reply to Wizertex from comment #0)

Expected results:

It should focus on the game automatically as in Google Chrome.

When pressing TAB, we exit the pointerLock mode, so do Chrome.
However, in Chrome it seems to enter pointerLock mode immediately right after user releases TAB, but we require users to click the mouse again.

Comment 4

[Edgar Chen [:edgar]]

bug 1627723 improves this a bit but still could be reproduced if holding TAB > 5 sec without pressing other keys or clicking the mouse.

Comment 5

[Edgar Chen [:edgar]]

(In reply to Edgar Chen [:edgar] from comment #4)

bug 1627723 improves this a bit but still could be reproduced if holding TAB > 5 sec without pressing other keys or clicking the mouse.

I wonder how Google Chrome handle this case.

Comment 6

[Edgar Chen [:edgar]]

It is because we don't treat TAB as a user gesture, but Google Chrome seems to treat it so.

Comment 7

[Edgar Chen [:edgar]]

Just found https://w3c.github.io/pointerlock/#dom-element-requestpointerlock saying,

Conversely, if pointer lock is exited via exitPointerLock() no engagement gesture is required to reenter pointer lock. This enables applications that frequently move between interaction modes, and ones that may do so based on a timer or remote network activity.