Closed
Bug 690068
Opened 14 years ago
Closed 14 years ago
highlighter and infobar should not be visible if node is not highlightable
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 10
People
(Reporter: dcamp, Assigned: paul)
References
Details
Attachments
(2 files)
6.64 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
6.91 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•14 years ago
|
||
Also, it feels like the box animates while it shrinks down to that pixel size, aren't the animations disabled while locked?
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → paul
Assignee | ||
Comment 2•14 years ago
|
||
I found another situation where the highlighter and/or the infobar are still visible when they should not (selecting a non-highlightable node after a highlightable node).
Summary: Tiny highlighter rect still visible when element is scrolled offscreen. → highlighter and infobar should not be visible if node is not highlightable
Assignee | ||
Comment 3•14 years ago
|
||
I think the infobar should be move to the top/left corner, bot be hidden.
Assignee | ||
Comment 4•14 years ago
|
||
- hide the highlighter borders if node not highlitable
- move the infobar to the top-left corner if node not highlitable
Attachment #566151 -
Flags: review?(rcampbell)
Assignee | ||
Updated•14 years ago
|
Status: NEW → ASSIGNED
Comment 5•14 years ago
|
||
Comment on attachment 566151 [details] [diff] [review]
patch v1
// node is not set or node is not highlightable, bail
- if (!this.node || !this.isNodeHighlightable(this.node)) {
- return;
- }
+ if (this.node && this.isNodeHighlightable(this.node)) {
I think I'd prefer to bail out early rather than nest the remainder of this method in an if { } block.
r+ with that reverted.
Attachment #566151 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 6•14 years ago
|
||
Well, actually, we don't want to bail out here. We want to execute:
> this.highlightRectangle(rect);
> this.moveInfobar();
(after the if block).
I think here I should only remove the comment.
Comment 7•14 years ago
|
||
(In reply to Paul Rouget [:paul] from comment #6)
> Well, actually, we don't want to bail out here. We want to execute:
>
> > this.highlightRectangle(rect);
> > this.moveInfobar();
>
> (after the if block).
>
> I think here I should only remove the comment.
OK, fair enough.
One thing I would like to see fixed though is the while(true) block. Can we replace that with something like:
while (!(frameWin.parent === frameWin || !frameWin.frameElement)) {
?
or do { ... } while() ?
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to Rob Campbell [:rc] (robcee) from comment #7)
> (In reply to Paul Rouget [:paul] from comment #6)
> > Well, actually, we don't want to bail out here. We want to execute:
> >
> > > this.highlightRectangle(rect);
> > > this.moveInfobar();
> >
> > (after the if block).
> >
> > I think here I should only remove the comment.
>
> OK, fair enough.
>
> One thing I would like to see fixed though is the while(true) block. Can we
> replace that with something like:
>
> while (!(frameWin.parent === frameWin || !frameWin.frameElement)) {
>
> ?
>
> or do { ... } while() ?
I don't see how I could do that.
Comment 9•14 years ago
|
||
ok, after another look, it looks like it'll be a pain to move that around, so don't worry about it.
Assignee | ||
Comment 10•14 years ago
|
||
removed the comfusing comment
Assignee | ||
Updated•14 years ago
|
Whiteboard: [land-in-fx-team]
Comment 11•14 years ago
|
||
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Comment 12•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 10
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•