Closed
Bug 1362135
Opened 9 years ago
Closed 9 years ago
White bar at bottom of screen with fullscreen youtube, vimeo, etc. On Galaxy Tab (4:3 aspect ratio)
Categories
(Firefox for Android Graveyard :: Audio/Video, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1377873
People
(Reporter: trondsg+bugzilla+mozilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
Build ID: 20161213175921
Firefox for Android
Steps to reproduce:
Go to fullscreen mode on a youtube or vimeo video.
Device: Samsung Galaxy Tab S2 8.
Firefox: Latest (53.0.1)
Actual results:
At the bottom there's a white / whitish (color #fafafa measured on a screenshot) bar. It has about the same thickness as the android status bar.
Expected results:
The video should be fullscreen, and the area around it black.
| Reporter | ||
Comment 1•9 years ago
|
||
Other people can see this: https://github.com/videojs/video.js/issues/3997
Updated•9 years ago
|
Component: Untriaged → Audio/Video
Product: Firefox → Firefox for Android
Comment 2•9 years ago
|
||
Hello and thanks for reporting!
I couldn't reproduce what you described but I got a different behavior: when I rotate the device from landscape to portrait or from portrait to landscape I see a white area at the bottom for 2-3 seconds.
Tested with Asus ZenPad 8(Android 6.0.1) and Samsung Galaxy Note 4 (Android 5.0.1).
Please install latest Nightly http://archive.mozilla.org/pub/mobile/nightly/2017/, and check if you get the same result.
Flags: needinfo?(trondsg+bugzilla+mozilla)
See Also: → 1303656
| Reporter | ||
Comment 3•9 years ago
|
||
It's working in Nightly (no white bar). :)
I still see a flash of white when rotating the screen.
Flags: needinfo?(trondsg+bugzilla+mozilla)
Comment 4•9 years ago
|
||
Based on comment 3 I will mark this bug as duplicate.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•