Closed
Bug 1516790
Opened 7 years ago
Closed 7 years ago
Release 64.0: The Menu Bar has completely disappeared. Attempting to restore it through Customize>Toolbars does nothing.
Categories
(Firefox :: Menus, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dilogsys, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Steps to reproduce:
Restart the machine to factor out possible Win 10 issue.
NB:
1. Winver 1607 Build 14393.3314 - fails
Also: Lenovo G510 laptop, I7/8Gb/480Gb SSD
2. 2nd machine, winver 1703 - works OK
3. 3rd machine, winver 1803 - works OK
Actual results:
No help. Still missing. Looks like a Win 10 1607/Firefox problem.
| Reporter | ||
Updated•7 years ago
|
Summary: Release 60.4: The Menu Bar has completely disappeared. Attempting to restore it through Customize>Toolbars does nothing. → Release 64.0: The Menu Bar has completely disappeared. Attempting to restore it through Customize>Toolbars does nothing.
| Reporter | ||
Comment 1•7 years ago
|
||
Opened a private window: Everything is OK!
Updated•7 years ago
|
Component: Untriaged → Menus
| Reporter | ||
Comment 2•7 years ago
|
||
Seems OK now.
Untriaged? What does that mean here? (I know what it means in medical terms.)
Comment 3•7 years ago
|
||
Can you provide the contents of about:support (hamburger button > help > troubleshooting information, click 'copy raw data to clipboard' on there, paste as an attachment in https://bugzilla.mozilla.org/attachment.cgi?bugid=1516790&action=enter to attach to the bug) to help triage this? Are you still seeing the issue? Can you provide a screenshot?
Flags: needinfo?(dilogsys)
| Reporter | ||
Comment 4•7 years ago
|
||
Problem went away for a few hours, returned next day.
Sending requested screen shot separately.
Flags: needinfo?(dilogsys)
| Reporter | ||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
(In reply to Daniel Feiglin from comment #4)
> Created attachment 9034276 [details]
> Mozilla_Menu_Bug.txt
Thanks. To be 100% sure, do you have any `userChrome.css` or `userChrome.js` files in your profile directory (there's a button on about:support to open the folder so you can check)?
> Problem went away for a few hours, returned next day.
> Sending requested screen shot separately.
Are there errors in the browser console (ctrl-shift-j) when this happens, and/or if you clear it, then press [done] in customize mode repeatedly, do new errors appear?
I'm a little confused about the screen shot. What's the blue arrow on top of the tab there?
Flags: needinfo?(dilogsys)
Comment 7•7 years ago
|
||
(In reply to :Gijs (he/him) from comment #6)
> Are there errors in the browser console (ctrl-shift-j) when this happens,
> and/or if you clear it, then press [done] in customize mode repeatedly, do
> new errors appear?
Realized this isn't very clear. I meant, when this is broken, if you open the browser console, enter customize mode, clear the browser console (use the trashcan/bin icon in the corner), and then click 'done', do new errors appear?
Also, when this is broken, if you open a second window, do new errors appear in the browser console?
| Reporter | ||
Comment 8•7 years ago
|
||
1. Opening a new browser window: There is no problem in the new window.
2. userChrome files - none.
Flags: needinfo?(dilogsys)
| Reporter | ||
Comment 9•7 years ago
|
||
3.I opened a second browser window - which looked OK: everything was there. I then killed the original window and worked for a while with the new one. I then closed it too.
4. Now the problem appears to have gone. Upon restarting FF (this session) all looks fine.
5. I'm trying one more thing: Cold-start reboot and then run FF. Back soon.
| Reporter | ||
Comment 10•7 years ago
|
||
6. Everything working normally.
Beats me!
It might be worth putting this ticket on hold at least until the next release (64.x, x>0). If all goes well (i.e. I don't start jumping up and down) you can close it.
Comment 11•7 years ago
|
||
OK, thanks for all the replies. If you see this again, if you could let us know about any related errors (see comment #6 / comment 7) then we can (will!) reopen and investigate further. Marking this as incomplete (ie we don't have enough information to investigate further at the moment) for now. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•