Blank space in fullscreen mode with navigation toolbar off and address bar on top
Categories
(Fenix :: Toolbar, defect)
Tracking
(firefox130 unaffected, firefox131 unaffected, firefox132+ fixed)
Tracking | Status | |
---|---|---|
firefox130 | --- | unaffected |
firefox131 | --- | unaffected |
firefox132 | + | fixed |
People
(Reporter: mstange, Assigned: mavduevskiy)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files, 3 obsolete files)
[Tracking Requested - why for this release]: Regression in release configuration that's currently mostly untested on Nightly
Steps to reproduce:
- Go to the settings, enable debug settings by tapping the Firefox logo in the about section, and turn off the navigation toolbar in the secret settings.
- Under Customize, pick "Top" for the address bar location
- Go to YouTube.
- Play any regular video (not a "short") in fullscreen mode.
Expected results:
The video should cover the entire screen.
Actual results:
There is a toolbar-sized blank space at the top.
I see this both on a Samsung Galaxy S21 running Android 14 and on Pixel 6 running Android 13.
This is a recent regression. Using mozregression:
12:15.80 INFO: Narrowed nightly regression window from [2024-09-10, 2024-09-12] (2 days) to [2024-09-10, 2024-09-11] (1 days) (~0 steps left)
12:15.81 INFO: Got as far as we can go bisecting nightlies...
12:15.81 ERROR: Sorry, but mozregression was unable to get a repository - no pushlog url available.
12:15.81 INFO: Newest known good nightly: 2024-09-10
12:15.81 INFO: Oldest known bad nightly: 2024-09-11
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ebf0e33ba93e&tochange=169a59fe35f8
Bug 1908639 seems like a good candidate. Petru, can you take a look?
Reporter | ||
Updated•2 months ago
|
Updated•2 months ago
|
Comment 1•2 months ago
|
||
If in fullscreen the toolbars should not be shown so there's no point in updating them.
Updated•2 months ago
|
Comment 2•2 months ago
|
||
Removing my NI, indeed, I've introduced the regression, sorry for it and thanks for the provided details @Markus!
Updated•1 month ago
|
Comment 3•1 month ago
|
||
We were already doing part of this.
Now we also reinitialize the toolbars to account for their different configurations when
the device is in portrait or landscape upon exiting fullscreen.
Comment 4•1 month ago
|
||
Previously if evaluating isFullscreen
inside FullScreenFeature's fullScreenChanged
callback
we would get the old value and not the current status of the tab.
This change fixes that.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 5•1 month ago
|
||
Talked with Mike about fixing this, he has a better approach that would fix another silent bug.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 6•1 month ago
|
||
Comment on attachment 9425484 [details]
Bug 1918757 - part 2 - Update FullScreenFeature to more eagerly update it's isFullscreen
property r=#android-reviewers
Revision D222587 was moved to bug 1919706. Setting attachment 9425484 [details] to obsolete.
Assignee | ||
Comment 7•1 month ago
|
||
Hidden in if's, there was a case where the function was not propagating height params to the EngineClippingBehaviour, but calculating toolbar height values itself. The problem was, that code didn't consider the fullscreen state. The height values passed to initiazlieEngineView functions are calculated with fullscreen state and tabstrip in mind.
The bug was hidden because onConfigChange didn't reinitialize engine view, but recently it started doing that.
Comment 9•1 month ago
|
||
bugherder |
Description
•