Closed
Bug 1406892
Opened 7 years ago
Closed 6 years ago
Hamburger menu glitches after trying to access the Library menu from the toolbar
Categories
(Firefox :: Menus, defect, P4)
Tracking
()
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | verified |
People
(Reporter: emilghitta, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [reserve-photon-structure])
[Affected versions]: Firefox 57.0b6 Firefox 58.0a1 [Affected platforms]: - Ubuntu 16.04 x64 [Unaffected platforms]: - Windows 10 64bit - macOS 10.11.6 [Steps to reproduce]: 1. Start Firefox. 2. Open the Hamburger menu. 3. Access the Library sub menu. 4. Click on the Library menu from the toolbar. [Expected result]: The Library menu from the toolbar is opened without issues. [Actual result]: The Library menu is not accessible after switching from the Hamburger menu. Also the Hamburger menu glitches while trying to repeat step 2. [Regression range]: This is a recent regression: Last good revision: af23e7b6eb9395aecf2a255316da782ca618750a First bad revision: 35acf942df34d075d1a181db6feeec0a9904f27b Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=af23e7b6eb9395aecf2a255316da782ca618750a&tochange=35acf942df34d075d1a181db6feeec0a9904f27b [Additional notes]: Form more information regarding this issue please observe the following screencast: https://drive.google.com/open?id=0BzOkHBmdnAoaUlBLQzFlbXVvQnM
Reporter | ||
Comment 1•7 years ago
|
||
Hi Mike! It seems that the fix for Bug 1401991 may have caused this regression. Can you have a look into this? Thanks!
Flags: needinfo?(mdeboer)
Updated•7 years ago
|
Whiteboard: [photon-structure] [triage]
Updated•7 years ago
|
Priority: -- → P4
Whiteboard: [photon-structure] [triage] → [reserve-photon-structure]
Comment 2•7 years ago
|
||
Might be that my patch in bug 1407591 also solves this glitch. I'll ask for verification once it lands.
Depends on: 1407591
Flags: needinfo?(mdeboer)
Updated•7 years ago
|
Flags: qe-verify+
Updated•6 years ago
|
Comment hidden (obsolete) |
Comment 4•6 years ago
|
||
(In reply to Panos Astithas [:past] (please ni?) from comment #3) > (In reply to Mike de Boer [:mikedeboer] from comment #2) > > Might be that my patch in bug 1407591 also solves this glitch. > > I'll ask for verification once it lands. > > Mike, this came up in regression triage today. Have you verified if your > patch fixed this yet?
Flags: needinfo?(mdeboer)
Comment 5•6 years ago
|
||
No, but I don't see this issue anymore, regardless. I consider this fixed, would be nice if Emil can verify it!
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mdeboer)
Resolution: --- → FIXED
Reporter | ||
Comment 6•6 years ago
|
||
Hi Mike! This issue is verified fixed using Firefox 60.0a1 (BuildId:20180302104326) on Ubuntu 16.04 64bit. It seems that this issue is reproducible using Firefox 59.0b14 (BuildId:20180301022608). Unfortunately,this issue seems to be riding to release 59.
status-firefox59:
--- → affected
status-firefox60:
--- → fixed
Comment 7•6 years ago
|
||
(In reply to Emil Ghitta, QA [:emilghitta] from comment #6) > Hi Mike! > > This issue is verified fixed using Firefox 60.0a1 (BuildId:20180302104326) > on Ubuntu 16.04 64bit. > > It seems that this issue is reproducible using Firefox 59.0b14 > (BuildId:20180301022608). > > Unfortunately,this issue seems to be riding to release 59. We already shipped this in 58, so this is unfortunate but I don't think there's much we can do at this point in the cycle. I expect some of Paolo's patches fixed this, but uplifting all of them to 59 at this point is too risky.
Updated•6 years ago
|
Comment 8•6 years ago
|
||
Based on Comment 6 and Comment 7, I am marking this issue as verified.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•