Closed Bug 342925 Opened 20 years ago Closed 20 years ago

browser.xul elements getting included in other XUL windows

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: tony, Assigned: mark)

Details

Attachments

(2 files)

XUL elements that appear to be specific to browser.xul are getting included in other Chrome windows. For example, if I open the JS console, then examine it with the DOM inspector, I see lots of browser.xul specific elements. See attached screenshots. This doesn't seem to happen on all XUL windows. E.g., if I point the DOM inspector at itself, there are no extra elements.
Summary: XUL elements getting included in all windows → browser.xul elements getting included in other XUL windows
Attached image linux —
linux DOM inspector pointing at JS console
Attached image mac —
Mac DOM inspector pointing at JS Console
Some (all?) of this is probably due to the menu overlays that are there to make the mac menus work (see browser/base/content/baseMenuOverlay.xul).
Sorry, I meant macBrowserOverlay.xul.
Tony, this is all about the mac menubar (for non-browser windows, this also means the hidden window)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
It's also pulling in unrelated things, e.g., the safe browsing JS file is getting loaded as well. Is there a way to control what gets pulled in and what doesnt? That is, maybe I shouldn't be loading the safe browsing code from global-scripts.inc.
I would load the safe browsing script files from browser.xul via <script/> elements (this isn't as slow as loadSubScript).
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: