Closed Bug 305691 Opened 20 years ago Closed 19 years ago

DOM Inspector tries to load overlays that don't exist in Firefox (chrome://communicator/content/...)

Categories

(Other Applications :: DOM Inspector, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 361105

People

(Reporter: jruderman, Unassigned)

References

()

Details

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050823 Firefox/1.0+ Steps to reproduce: 1. Open DOM Inspector. Result: The following warnings/messages appear in the JavaScript console, but the DOM Inspector works anyway. No chrome package registered for chrome://communicator/content/utilityOverlay.xul . Warning: Failed to load overlay from chrome://communicator/content/utilityOverlay.xul. Source File: chrome://inspector/content/inspector.xul Line: 0
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050830 Firefox/1.6a1 ID:2005083018 When DOM-I is opened, Fx-trunk on WIn-XP also shows the same worning as Warning: Failed to load overlay from chrome://communicator/content/utilityOverlay.xul. Source File: chrome://inspector/content/inspector.xul Line: 0
This is because our dear friends in Aviary land decided they didn't need chrome://communicator/anything. A little preprocessing seems the only solution, unless you want to break SeaMonkey users.
On the other hand, domi tries to load a toolkit overlay in SeaMonkey: Warning: Failed to load overlay from chrome://browser/content/baseMenuOverlay.xul. Source File: chrome://inspector/content/inspector.xul Line: 0
SeaMonkey complain in all of the windows (Navigator, MailNews, ChatZilla, JS Console, you name it) about a XUL error: <menuitem id="menu_inspector" label="&inspectorTaskCmd.label;" and DOMI is not available in the Tools menu. Knowing how to turn off other locales would be handy, too.
Whoops, I missed this when I filled Bug 361105 apparently. Patch will be in other bug shortly. *** This bug has been marked as a duplicate of 361105 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
You need to log in before you can comment on or make changes to this bug.