Other Applications
DOM Inspector
12 years ago
11 years ago


(Reporter: smontagu, Unassigned)


({dogfood, qawanted})

dogfood, qawanted

Firefox Tracking Flags

(Not tracked)




12 years ago
In a trunk build from this morning the DOM nodes view comes up blank. This is a recent regression, maybe from bug 210246

Comment 1

12 years ago
From error console:
Error: [Exception... "Could not convert JavaScript argument"  nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)"  location: "JS frame :: chrome://inspector/content/viewers/dom/dom.js :: DOMViewer :: line 86"  data: no]
Source File: chrome://inspector/content/viewers/dom/dom.js
Line: 86
Fine here

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060620 Minefield/3.0a1 ID:2006062005
I tried backing out bug 210246 and that didn't help...

This is blocking me working on at least two bugs, so it'd really be nice to get some traction here.  :(
Severity: normal → major
Keywords: qawanted
So I bet this is a consequence of a dep build after the inspector move -- I'm seeing QI to nsITreeView fail on an inDOMView over here, with the inDOMView code living in  I'll try clobbering.

Comment 5

12 years ago
Most likely: shouldn't exist any more
Yeah, clobbering helps...
Blocks: 325100

Comment 7

12 years ago
Clobbering helps for me too, so I suppose I can close this, but I wish it could have been avoided :(
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
it might've been enough to delete
It wasn't.  I tried that.

Comment 10

12 years ago
Note for the enduser who doesn't know what a clobber build means:

1. Shutdown SeaMonkey/Firefox/whatever.
2. In the application components directory:
2.1. Delete inspector.dll or or libinspector.dylib
2.2. Delete compreg.dat/xpti.dat
3. Restart. 
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.