Closed
Bug 307255
Opened 20 years ago
Closed 20 years ago
DOM Inspector "blink selected element" wrong on startup if "show whitespace nodes" is false
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aguertin+bugzilla, Unassigned)
References
Details
(Keywords: fixed1.8.0.1, fixed1.8.1, regression)
Attachments
(2 files)
|
504 bytes,
patch
|
Details | Diff | Splinter Review | |
|
594 bytes,
patch
|
bzbarsky
:
review+
mtschrep
:
approval1.8.0.1+
mtschrep
:
approval1.8.1+
|
Details | Diff | Splinter Review |
DOM Inspector "blink selected element" is no longer the default, and doesn't
stick between times you open it. This is an immensely annoying regression.
Hmm... as I write this I notice that inspector.blink.on = true, and flipping it
twice turns it on. So it looks like it's not checking the pref each time I start
it up.
Regression range coming.
| Reporter | ||
Comment 1•20 years ago
|
||
Er, nevermind. It works with a clean profile.
But the pref is correct, so why... ARGH.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•20 years ago
|
||
AHA! The "show whitespace nodes" pref is wrongly interacting with "blink
selected element". Basically, if you have "show whitespace nodes"=false, "blink
selected element" will be false on startup, regardless of what its actual value is.
Reopening, changing summary, etc. And I will find that regression range.
Severity: normal → minor
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: DOM Inspector "blink selected element" no longer default, doesn't stick → DOM Inspector "blink selected element" wrong on startup if "show whitespace nodes" is false
| Reporter | ||
Comment 3•20 years ago
|
||
Regressed between 2005-08-19-06 and 2005-08-20-06 on trunk, I assume the same
time for branch. I don't see anything that looks like a likely culprit,
unfortunately.
Comment 4•20 years ago
|
||
I tracked this down to bug 303981
With builds with the bug, I get this:
[Exception... "'[JavaScript Error: "this.mDOMView.selection has no properties"
{file: "chrome://inspector/content/viewers/dom/dom.js" line: 630}]' when calling
method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "<unknown>" data: yes]
Depends on: 303981
Version: unspecified → Trunk
| Reporter | ||
Comment 5•20 years ago
|
||
Can this block 1.8b5? It's a regression that's been tracked down to the checkin
that regressed it, and for web developers with certain configurations, it has
the potential to be a real pain.
Flags: blocking1.8b5?
Comment 6•20 years ago
|
||
If we get a fix for this that's low risk and has appropriate reviews, we may
consider this but I don't think we're going to block on this.
Flags: blocking1.8b5? → blocking1.8b5-
| Reporter | ||
Comment 7•20 years ago
|
||
I believe I have figured out the cause of this bug, though it's entirely
possible I'm dead wrong, since I really have no idea what I'm doing.
In dom.js
http://lxr.mozilla.org/mozilla1.8/source/extensions/inspector/resources/content/viewers/dom/dom.js#121
initialize does this:
this.setAnonContent(PrefUtils.getPref("inspector.dom.showAnon"), false);
this.setWhitespaceNodes(PrefUtils.getPref("inspector.dom.showWhitespaceNodes"));
this.setFlashSelected(PrefUtils.getPref("inspector.blink.on"));
But if setWhitespaceNodes finds it doesn't need to change anything...
http://lxr.mozilla.org/mozilla1.8/source/extensions/inspector/resources/content/viewers/dom/dom.js#217
...it returns, and initialize never _gets_ to setFlashSelected.
So this could be fixed either by moving setFlashSelected above
setWhitespaceNodes, or by changing setWhitespaceNodes so it doesn't return
unnecessarily.
| Reporter | ||
Comment 8•20 years ago
|
||
This patch uses the first method, since the second is beyond me.
Comment 9•20 years ago
|
||
So, this one eventually annoyed me sufficiently to look into it. Both
dolphinling and ajschult have a grasp at different parts of the problem. What's
happening is that ajschult's exception (which appears to be genuine, and not
caused by bug 303981) is causing setFlashSelected to be skipped.
By comparison setAnonContent does not throw an exception, as it uses an aReload
parameter. It seems to me that setWhitespaceNodes should use the same system.
Comment 11•20 years ago
|
||
This is easier than fiddling around with QI.
Attachment #199929 -
Flags: review?(Jan.Varga)
Comment 12•20 years ago
|
||
Comment on attachment 199929 [details] [diff] [review]
Get the selection from the tree view
r=bzbarsky, dammit. This was pissing me off too.
Neil, do you want to land this? Fwiw, I think we should get this in on branch.
Attachment #199929 -
Flags: review?(Jan.Varga)
Attachment #199929 -
Flags: review+
Attachment #199929 -
Flags: approval1.8.0.1?
Comment 13•20 years ago
|
||
Fix checked in to the trunk.
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
Comment 14•19 years ago
|
||
Comment on attachment 199929 [details] [diff] [review]
Get the selection from the tree view
Please land on 1.8 and 1.8.1 branches. Thanks!
Attachment #199929 -
Flags: approval1.8.1+
Attachment #199929 -
Flags: approval1.8.0.1?
Attachment #199929 -
Flags: approval1.8.0.1+
Comment 15•19 years ago
|
||
*** Committing to MOZILLA_1_8_BRANCH...
new revision: 1.35.4.1; previous revision: 1.35
*** Committing extensions/inspector/resources/content/viewers/dom/dom.js on MOZILLA_1_8_0_BRANCH...
new revision: 1.35.12.1; previous revision: 1.35
Keywords: fixed1.8.0.1,
fixed1.8.1
Updated•18 years ago
|
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.
Description
•