Firefox hangs when trying to play a video in full-screen mode
The bug seems to appear out of nowhere. A couple of days ago firefox started hanging at sudden moments. Now I've come across this: I open a .mp4/YouTube/other video, it starts playing nicely. But then, after I press a full-screen button (or the "F" key) , firefox hangs, which means: video player controls seem inanimate (the video continues playing non full-screen though), browser tabs act like they're a static picture (but if I press CTRL + T many times and then close it with a keybinding, it shows the message askingi if i'm sure I want to close my N tabs). All the logs I'm conscious about are here: https://hastebin.com/sogaheviju.sql
被選擇的解決方法
Okay I've fixed that. Turns out my Window manager had a buggy code in it.
從原來的回覆中察看解決方案 👍 0所有回覆 (3)
built-in controls let you expand embedded videos so that they take up your whole screen. This article shows you how to turn "full screen mode" on and off at the touch of a button.
Here's how to do it:
When you tap on a supported video, the full screen icon will show up on the video controls. Tap on it to expand the video:
android expand video
To shrink the video back to its original size, tap the full screen icon again:
android original size
Tip: Once you're in full screen mode, you can rotate your device to change the video's display orientation.
davidspriggs said
built-in controls let you expand embedded videos so that they take up your whole screen. This article shows you how to turn "full screen mode" on and off at the touch of a button. Here's how to do it: When you tap on a supported video, the full screen icon will show up on the video controls. Tap on it to expand the video: android expand video To shrink the video back to its original size, tap the full screen icon again: android original size Tip: Once you're in full screen mode, you can rotate your device to change the video's display orientation.
My friend, I know HOW to open the video full screen. Not that it helps to solve the problem.
選擇的解決方法
Okay I've fixed that. Turns out my Window manager had a buggy code in it.