Closed
Bug 158792
Opened 22 years ago
Closed 22 years ago
click-select-node no longer works; tree view not updated on URL loads
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: hwaara)
References
Details
(Keywords: regression)
Attachments
(2 files, 1 obsolete file)
49.74 KB,
image/jpeg
|
Details | |
1.04 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
This is a regression from the fix for bug 156072. Backing out the dom.js change fixes it. There are two problems: 1) The "Find a node to inspect by clicking on it" functionality does not work 2) Typing a url in the urlbar (in inspector) and hitting enter does not update the top-left DOM tree view immediately. It ends up waiting on some event or something... There are no errors in the JS console.
Reporter | ||
Updated•22 years ago
|
Keywords: mozilla1.1,
regression
another strange thing is that clicking the document node opens a DOM-inspector in the "nodeinfo-pane". Kind'a hard to describe, have a look at the screenshot
Reporter | ||
Comment 2•22 years ago
|
||
jst says this may be due to some code somewhere QIing to nsIContent; documents implement nsIDOMNode but not nsIContent....
Reporter | ||
Comment 3•22 years ago
|
||
*** Bug 159079 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 4•22 years ago
|
||
So.... we need to call selectElementInTree on the right thing in setInitialSelection(). This fixes the "can't click-select" and "view not updated" issues. _However_, when this is done the problem sicking noticed kicks in.... The live tree is on the _right_, not on the left. That's not so great. No idea yet why that's happening. A further issue is that even with this patch, if the #document node's twisty is collapsed and then we try to do click-to-select things break. The reason is that inDeepTreeWalker::ParentNode effectively skips over the #document node and runs up into XUL while looking for the tree root. This could be fixed by either hacking ParentNode() to somehow recognize that it has come to the root of the view _or_ by showing #document nodes as children of iframes and then having ParentNode() only jump for a _document_, not a documentElement. So the display would be something like: #document <?pi?> HTML BODY IFRAME #document <?pi?> HTML BODY Thoughts on that? We need to either fix this by a day or two from now or back out the dom.js changes from bug 156072; shipping 1.1 like this is unacceptable.
Reporter | ||
Comment 5•22 years ago
|
||
Attachment #92560 -
Attachment is obsolete: true
Reporter | ||
Comment 6•22 years ago
|
||
Comment on attachment 92800 [details] [diff] [review] backout patch this has r=caillon, rs=jst
Attachment #92800 -
Flags: superreview+
Attachment #92800 -
Flags: review+
Comment 7•22 years ago
|
||
Comment on attachment 92800 [details] [diff] [review] backout patch a=asa (on behalf of drivers) for checkin to 1.1
Attachment #92800 -
Flags: approval+
Reporter | ||
Comment 8•22 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → 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
•