[Fission] - video-streams from https://gamingforgood.net/ cannot be toggled to fullscreen
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
Fission Milestone | M5 |
People
(Reporter: cfogel, Unassigned)
References
Details
Affected versions
- 71.0a1 (2019-10-16)
Affected platforms
- Windows 10, macOS 10.14, Ubuntu 16.04;
Steps to reproduce
Preconditions:
- fission.autostart set to true;
- Access https://gamingforgood.net/s/staysafetv or any other stream from the website;
- Enable the audio for the stream(or wait 3-5 seconds);
- Click on the Fullscreen button for the stream;
Expected result
- stream goes fullscreen;
Actual result
- button is toggled but fullscreen does not go through;
Regression range
- will check if one asap;
Comment 1•5 years ago
|
||
I tried to find a regression for this issue but I found that this is not a regression due to the fact that the fission.autostart
option from the about:config
menu was not visible in earlier versions of FX. Here is a pushlog from where the issue is reproducible https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ce56e2779818d25cfa2ac32f38ed84e6811d76a9&tochange=7e01c4d1cddcbbd4375fbd8b8909249b9ecb4eb6
.
Comment 2•5 years ago
|
||
Fullscreen for Fission was done in bug 1505916. Abdoulaye, will you have some time to look into this?
Comment 3•5 years ago
|
||
Neha: this might be related to SetActiveWindow issue with Fission subframes. I will need a closer look to confirm.
Comment 4•5 years ago
|
||
Now, I can safely say this is a duplicate of Bug 1556627. Actually, if you move the focus (with Tab) to the subframe containing the video, fullscreen should work.
Moving the focus to that subframe can be irksome since there are a lot of elements in https://gamingforgood.net pages. So I have a simpler test case:
- Open http://fission-project.000webhostapp.com/html/test_fullscreen.html.
- unmute video
- Press tab once
- Click the "Enter fullscreen" button.
Updated•5 years ago
|
Comment 5•4 years ago
|
||
Thanks Abdoulaye. I'll mark this dependent on Bug 1556627 but will keep it open for now to ensure we verify once the focus patch lands.
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Now that bug 1556627 is done, could we reverify that this is indeed fixed?
Reporter | ||
Comment 7•4 years ago
|
||
Yes, it is working fine now.
Verified with 75.0a1 (2020-02-19) - Windows 10, macOS 10.15.3, Ubuntu 19.04.
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Description
•