Closed
Bug 158766
Opened 22 years ago
Closed 22 years ago
using url field in inspector doesn't provide a dom
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: timeless, Assigned: sicking)
Details
(Keywords: regression)
Attachments
(1 file)
10.72 KB,
text/plain
|
Details |
2002072008 inspect window fills the dom view pane, but entering a url in the location field doesn't.
Comment 1•22 years ago
|
||
Error: uncaught exception: Security Error: Content at http://bugzilla.mozilla.org/ may not load data from chrome://inspector/content/inspector.xul.
Keywords: regression
ok apparently this isn't 100% reproducable. i'll try to track down more complete steps, however given that caillon experienced it, i assert that i wasn't hallucinating.
Comment 4•22 years ago
|
||
Sicking asked me to upload this stack -- this is in nsRange::SetStart() We're failing here: if (!nsContentUtils::CanCallerAccess(aParent)) { return NS_ERROR_DOM_SECURITY_ERR; }
Assignee | ||
Comment 5•22 years ago
|
||
I don't fully understand what's happening here, but my guess is that the js-stack isn't fully set up so we end up comparing against the wrong url. It also seems that this doesn't happen on all pages, probably only ones containing javascript. It happens for me on http://bugzilla.mozilla.org but not on http://www.mozilla.org
Assignee | ||
Comment 6•22 years ago
|
||
oh, and the DOM does show up, at least for me. But the exception is worrying anyway
Assignee | ||
Comment 7•22 years ago
|
||
Note that the only problem mentioned in this bug that is related to bug 156452 is the fact that an exception is thrown. Both the missing nodeinfo view and the extra DOM-tree is from something else (and might even be by design for all i know)
Comment 8•22 years ago
|
||
It's not by design.
I don't think this bug was meant to be nsbeta1+. DOM Inspector is not shipped by Netscape as far as I know.
Assignee | ||
Comment 10•22 years ago
|
||
is this fixed?
Updated•20 years ago
|
Product: Core → Other Applications
Updated•17 years ago
|
QA Contact: timeless → dom-inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•