Open Bug 1416532 Opened 7 years ago Updated 1 month ago

All menu names disappear and unable to open new windows if the browser console is the only window open

Categories

(DevTools :: Console, defect, P3)

55 Branch
defect

Tracking

(firefox-esr52 wontfix)

Tracking Status
firefox-esr52 --- wontfix

People

(Reporter: cpeterson, Unassigned)

Details

Attachments

(1 obsolete file)

STR:
1. Open Firefox with one browser window.
2. Open the browser console window with Cmd+Shift+J.
3. Close the browser window.
4. Try to open a new browser window with Cmd+N.

RESULT:
Nothing happens. No new browser window opens. All of Firefox's menu names in the macOS menu bar are gone except for the "Firefox" application menu.

If you close the browser console window, then all the Firefox menu names reappear and you can open new browser windows with Cmd+N.

I have only tested on macOS. I can reproduce this behavior in ESR 52, so this is not a regression.
I think this has always been the behavior. I tried changing the 'features' string for opening the browser console window (https://searchfox.org/mozilla-central/source/devtools/client/webconsole/hudservice.js#218) but I don't see any difference even when adding 'menubars', for instance. I guess the issue here is that we aren't actually loading browser.xul and are loading webconsole.xul which doesn't register the menu items. But based on the documentation here it seems we should be able to add normal window.open features: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIWindowWatcher#openWindow().

Gijs, am I missing something obvious? Is there a way to force the webconsole window to load 'within' browser.xul similar to what happens when we call window.open from a web page?
Flags: needinfo?(gijskruitbosch+bugs)
(In reply to Brian Grinstead [:bgrins] from comment #1)
> Gijs, am I missing something obvious? Is there a way to force the webconsole
> window to load 'within' browser.xul similar to what happens when we call
> window.open from a web page?

There is, but then you'd get all the toolbars and so on as well, and the chrome URI would just load in a tab. That doesn't seem desirable.

I think you might want to look at how the library window solves this issue. I believe there's a base menu overlay you can include, and then you may need some script files (maybe "just" browser.js and/or utilityOverlay.js and friends?) to make it work.
Flags: needinfo?(gijskruitbosch+bugs)
Product: Firefox → DevTools
Severity: normal → S3
Attachment #9381617 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: