Menubar often has no menus when clicking a link (with Firefox as default browser)
Categories
(Firefox :: Menus, defect)
Tracking
()
People
(Reporter: zzy, Unassigned)
Details
Attachments
(2 files)
Screen Shot 2020-03-03 at 1.52.43 PM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
macOS Catalina 10.15.3, Firefox 73.0.1
- Make sure Firefox is your default browser, and "Open links in tabs instead of new windows" is enabled
- Quit Firefox
- Click a link in another app, like a 3rd party Twitter client, or Slack
Actual results:
Firefox launches, but the link is opened in a new window instead of a new tab. When that new window is active, there are no visible menu items in the menubar (though if you select the Apple menu and drag the cursor to the right, you see a lot of null menus exist but are too tiny to be visible).
Switching back to my other main window full of tabs restores the File, Edit, View, etc. menus.
Expected results:
The link should be opened in a new tab, and the menubar should be unaffected.
Well that's odd. When reproducing the bug to create the attached screenshots, something different happened for the first time: I got a new window with an empty tab, the link I clicked ended up as a tab in my main window, but strangely, the menubar now disappears when my main window is active, and if I switch to the new window with the empty tab, I get the menubar back.
Regardless, if I quit and relaunch Firefox manually, my Firefox menubar comes back.
Also, in case it's relevant: I'm running three add-ons, "Ghostery - Privacy Ad Blocker", "uBlock Origin", and "uMatrix".
|
||
Comment 5•5 years ago
|
||
Can you reproduce this in Safe Mode? You can get to Safe Mode by going to the Firefox menu, then clicking on Help, then "Restart with Add-ons Disabled..."
I can't use "Restart With Add-ons Disabled" because the bug repro steps depend on Firefox launching in response to clicking a link in another application.
But I went into Add-Ons and manually turned them off, and the bug still reproduces.
|
||
Comment 7•5 years ago
•
|
||
This is a known issue that's (mostly) fixed in 74 which is being released this week.
Description
•