Closed
Bug 766107
Opened 13 years ago
Closed 13 years ago
Inspector errors and does not close after attempting to inspect content in Thimble.
Categories
(DevTools :: Inspector, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 761251
People
(Reporter: bugs, Unassigned)
References
()
Details
To reproduce, load Thimble with Inspector closed, right click on the <title> text on the left and choose Inspect.
Then click the close X in the lower right.
The bottom window closes, but not the side one.
The following errors were noted in the javascript console.
Error: TypeError: can't access dead object Source File: resource:///modules/devtools/LayoutView.jsm Line: 294
Error: TypeError: aContext is null Source File: resource:///modules/devtools/StyleInspector.jsm Line: 46
Error: TypeError: domRules is null Source File: resource:///modules/devtools/CssRuleView.jsm Line: 162
Tested in latest Nightly.
BTW. There's a possibly related error noted in both Firebug and Inspector where right clicking on that <title> in the editor displayed not that tag in the context of the full page, but rather just its own little snippet as if it had been removed from the page in JS.
Specifically, the following.
<pre><span class="cm-tag"><title></span>Your Awesome Webpage<span class="cm-tag"></title></span></pre>
If I right click on it, and choose inspect again, in either Firebug or Inspector, it displays correctly.
BTW, I installed Firebug upon noticing the Inspector, this was in all other respects a clean profile created a couple of days ago, and only used on a handful of sites.
Oh, and once this occurs, I can't find any way to close Inspector. Even if I go to another site, choose Inspect, hit close, it still refuses to close.
The only fix seems to be to restart the browser.
I did test Inspector on various other pages (google.com, about:home) and it seemed to work and close just fine.
Comment 2•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•