Closed
Bug 1282763
Opened 10 years ago
Closed 9 years ago
Tab Tray Menu is misplaced on rotation
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox48 wontfix, firefox49 wontfix, firefox50 wontfix, firefox51 wontfix, firefox52 wontfix, firefox53 verified)
VERIFIED
FIXED
Firefox 53
People
(Reporter: TeoVermesan, Assigned: twointofive)
References
Details
Attachments
(1 file)
Steps to reproduce:
1. Open Firefox in portrait
2. Open the tab tray
3. Tap the 3 dots button near the "+" button
4. Rotate from portrait to landscape
Expected results:
- "New Private Tab" and "Close all Tabs" dialog is displayed over the "+" and 3 dots button
Actual results:
- "New Private Tab" and "Close all Tabs" dialog is displayed under the header
| Comment hidden (mozreview-request) |
I don't expect this is high priority, but I was just in the TabsPanel code, so ... here it is. I wonder if something similar is going on in bug 1318672.
Assignee: nobody → twointofive
| Comment hidden (mozreview-request) |
Comment 4•9 years ago
|
||
| mozreview-review | ||
Comment on attachment 8815835 [details]
Bug 1282763 - Wait for anchor to display before reanchoring tabs menu.
https://reviewboard.mozilla.org/r/96612/#review99392
Attachment #8815835 -
Flags: review?(s.kaspari) → review+
Pushed by twointofive@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/073efe219a15
Wait for anchor to display before reanchoring tabs menu. r=sebastian
Comment 6•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox53:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 53
Comment 7•9 years ago
|
||
We will let it ride the trains.
status-firefox51:
--- → wontfix
status-firefox52:
--- → wontfix
Comment 8•9 years ago
|
||
Verified as fixed in Nightly build 53.0a1 2017-01-09;
Devices:
-Asus ZenPad (Android 6.0.1);
-LG G4 Android 5.1;
-Lenovo A536 Android 4.4.2.
Status: RESOLVED → VERIFIED
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
•