1781732 - CTRL + T from a fullscreen YouTube video does not focus the search bar

Status: NEW

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

Description

[4P5]

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

Steps to reproduce:

• Open a YouTube video and make it fullscreen.
• Press CTRL + T to create a new tab.
• Attempt to type a query.

Actual results:

Nothing is typed; I must manually click on the address bar to begin typing.

Expected results:

Normally, opening a new tab immediately focuses the address bar and allows the user to type.

Comment 1

[Alice0775 White]

another str:

1. Open using dom fullscreen page (e.g https://davidwalsh.name/demo/fullscreen.php )
2. enter fullscreen
3. Ctrl+T

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=cc263dfb7b13&tochange=b867bb9c50ee

Comment 2

[Hsin-Yi Tsai (she/her) [:hsinyi]]

CC Edgar that he may know what's up here.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1160014

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

:xidorn, since you are the author of the regressor, bug 1160014, could you take a look?
For more information, please visit auto_nag documentation.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 6

[Xidorn Quan [:xidorn] UTC+11]

I'll take a look over the weekend.

Comment 7

[Xidorn Quan [:xidorn] UTC+11]

I tested Firefox 41 and 42 on Windows 10 and 11, and it doesn't seem to work the same way as they do today. In all the combinations, the fullscreen state is not complete, there is no fullscreen warning shown, and the chrome is still showing. I guess the code back then somehow no longer works on the systems correctly nowadays. However, in all those combinations I can reproduce this issue, although given the weirdness, I'm not sure whether the result makes sense.

Alice, do you have some tip on reproducing this on Windows? Do you have some special settings? What Windows version are you using?

I also noticed that this is reproducible on Linux as well, and I can reproduce it on Firefox 41 but not 40 (and on Windows, Firefox 40 didn't have the weirdness mentioned above, and it didn't have this issue either), so I did another bisect, and the regression window seems to be https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0093691d3715&tochange=b7ee8e13145a

There are two changes possibly related: bug 1168028 and bug 1173866. Not sure which one causes this, though.

Comment 8

[Xidorn Quan [:xidorn] UTC+11]

(The weirdness mentioned in the previous comment seems to start from https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8b64c75b0b86&tochange=62d9b117c688 and end in https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=04b8c412d9f58fb6194c58dcaa66bf278bbd53cf&tochange=f61c3cc0eb8b7533818e7379ccc063b611015d9d. None of which has fullscreen related changes. Not sure what is the problem there.)

Comment 9

[Alice0775 White]

(In reply to Xidorn Quan [:xidorn] UTC+11 from comment #7)

Alice, do you have some tip on reproducing this on Windows? Do you have some special settings? What Windows version are you using?

No, nothing is special in Firefox. I tested with build of mozilla-central and inbound.
I think the difference is Windows10 animation setting. I have disabled Show animations in Windows in Settings > Ease Of Access settings.