Closed
Bug 958456
Opened 12 years ago
Closed 12 years ago
[Highlighter] Hovering over comment nodes should make the highlighter disapear
Categories
(DevTools :: Inspector, defect)
DevTools
Inspector
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 29
People
(Reporter: pbro, Assigned: pbro)
Details
(Whiteboard: [good first verify])
Attachments
(1 file, 1 obsolete file)
|
6.99 KB,
patch
|
pbro
:
review+
|
Details | Diff | Splinter Review |
Steps to reproduce :
1 Go to http://www.mozilla.org/en-US/
2 Open Devtools Inspector Panel
3 In this panel, mouse hover #outer-wrapper. The highlighter correctly display #outer-wrapper in the main window.
4 In the Inspector Panel, now mouse hover the "<!-- close #outer-wrapper -->" just below. The highligher still displays #outer-wrapper.
Expected: the hightligher shoud disappear on hover HTML comment nodes.
| Assignee | ||
Comment 1•12 years ago
|
||
Paul,
This patch is 2 lines of code!
+ a test of course.
ongoing try: https://tbpl.mozilla.org/?tree=Try&rev=083162024128
Attachment #8359797 -
Flags: review?(paul)
| Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 8359797 [details] [diff] [review]
bug958456-hide-highlighter-on-comments.patch
Joe, Paul isn't going to have time right now to review this.
Attachment #8359797 -
Flags: review?(paul) → review?(jwalker)
Comment 3•12 years ago
|
||
Comment on attachment 8359797 [details] [diff] [review]
bug958456-hide-highlighter-on-comments.patch
Review of attachment 8359797 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/devtools/inspector/test/browser_inspector_bug_958456_highlight_comments.js
@@ +54,5 @@
> + yield hoverElement("#id4");
> + assertHighlighterHidden();
> +
> + finishTest();
> + }).then(null, Cu.reportError);
This is mega picky, but since we're working out pattern for Task.jsm, you could also do:
}).then(null, Cu.reportError).then(finishTest);
Which has the advantage that if one of the assert functions throws an exception, then the test fails rather than hanging.
Does Cu.reportError actually fail the test?
I wonder if we should have a convention of some boiler plate like:
function test() {
return Task.spawn(realTest).then(null, ok.bind(null, false)).then(finishTest);
}
Attachment #8359797 -
Flags: review?(jwalker) → review+
| Assignee | ||
Comment 4•12 years ago
|
||
Thanks Joe. I changed the test as advised. Indeed it's a better pattern.
Applied the R+ on this new patch.
Attachment #8359797 -
Attachment is obsolete: true
Attachment #8361760 -
Flags: review+
| Assignee | ||
Comment 5•12 years ago
|
||
Try is green, going to check this in fx-team.
| Assignee | ||
Comment 6•12 years ago
|
||
Fixed in fx-team: https://hg.mozilla.org/integration/fx-team/rev/60395c47c63b
Whiteboard: [fixed-in-fx-team]
Comment 7•12 years ago
|
||
Assignee: nobody → pbrosset
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 29
Updated•12 years ago
|
Whiteboard: [good first verify]
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•