Closed
Bug 1908028
Opened 8 months ago
Closed 8 months ago
[toolbar redesign] cookie banner doesn't adjust to orientation change
Categories
(Fenix :: Toolbar, defect)
Tracking
(firefox130 fixed)
RESOLVED
FIXED
130 Branch
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: mavduevskiy, Assigned: mavduevskiy)
References
Details
Attachments
(2 files)
Steps to reproduce
- Open cookieserve.com
- Observe a cookie banner being positioned at the top of the toolbar
- Rotate the device to landscape mode
Expected behavior
The banner should be positioned at the very bottom of the screen
Actual behavior
The banner keeps spacing from the bottom of the screen, at the size of the navbar
Device information
- Firefox version: 130
- Android device model: pixel 7
- Android OS version: 14
Any additional information?
Assignee | ||
Updated•8 months ago
|
Assignee: nobody → mavduevskiy
Assignee | ||
Updated•8 months ago
|
Summary: [toolbar redesign] cookie banner don't adjust to orientation change → [toolbar redesign] cookie banner doesn't adjust to orientation change
Assignee | ||
Comment 1•8 months ago
|
||
When the navbar is on, the content spacing isn't set properly for landscape mode (if the app launches in landscape mode), and doesn't get updated on the orientation change.
Updated•8 months ago
|
Attachment #9412893 -
Attachment description: Bug 1908028 - Fix content padding issue on orientation change → WIP: Bug 1908028 - Fix content padding issue on orientation change
Updated•8 months ago
|
Attachment #9412893 -
Attachment description: WIP: Bug 1908028 - Fix content padding issue on orientation change → Bug 1908028 - Fix content padding issue on orientation change
Pushed by mavduevskiy@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/68b629962ae1
Fix content padding issue on orientation change r=android-reviewers,Roger
Comment 4•8 months ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 8 months ago
status-firefox130:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•