Closed
Bug 469391
Opened 16 years ago
Closed 16 years ago
Fix seizure-inducing flicker when inspector is hovered on element boundaries
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tracy, Assigned: whimboo)
Details
Attachments
(1 file)
833 bytes,
patch
|
Details | Diff | Splinter Review |
MozMill with the Inspector enable goes into wicked flickering when mousing over boundaries of various elements. STR: 1) Open the default Firefox start page. anything will work actually even inside MozMill interface. 2) slowly move the mouse around until you're hovering over the edge of an element Tested results: The outline of the elements vying for attention flicker back and forth and the UI in MozMill UI of inspector and View pane allows dance in attempt to report the element data for both elements Expected results: no seizure inducing flickering in either app content outlining nor in the MozMill UI.
Comment 1•16 years ago
|
||
For the elements that would flicker, I am now not outlining them in blue and instead just displaying the locator.. everything else will be outlined as usual. If people could give this a try and let me know if it's better that would be helpful.
Comment 2•16 years ago
|
||
Is this fixed?
Comment 3•16 years ago
|
||
Haven't had any complains since I checked in this code, so I am assuming the solution did the trick.. go ahead and mark this fixed.
Assignee | ||
Comment 4•16 years ago
|
||
It flickers heavily while hovering over the tab buttons beneath the inspector output, e.g. the Event button. Further the lines are moving some pixels while hovering over the output pane. I believe that the output pane shouldn't be automatically resized. Can't we give it a fixed height and show scroll bars if needed?
Assignee | ||
Comment 5•16 years ago
|
||
To avoid flickering on webpages we should use outline instead of border. Outline doesn't add extra pixels around the element. inspectElement in inspection.js should be changed to following code: //Element hilighting if (e.type == "mouseover"){ try { if (this.lastEvent){ this.lastEvent.target.style.outline = ""; } this.lastEvent = e; e.target.style.outline = "1px solid darkblue"; } catch(err){} } else { e.target.style.outline = ""; }
Assignee | ||
Comment 6•16 years ago
|
||
This will fix the elements jumping issue on websites and for browser chrome.
Attachment #355656 -
Flags: review?(mrogers)
Updated•16 years ago
|
Summary: Fix seizure inducing flicker when inspector is hovered on element boundaries → Fix seizure-inducing flicker when inspector is hovered on element boundaries
Comment 7•16 years ago
|
||
This worked like a charm, thanks so much Henrik, I had no idea the outline property even existed. Checked into trunk and tested.
Assignee | ||
Comment 8•16 years ago
|
||
You are welcome! Adam, can you take the review request and close this bug as fixed? Or are there any other issues to resolve? I should file a new bug for the inspector output flickering, right?
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Comment 9•16 years ago
|
||
I actually don't have access to close this, can someone look into that? I'm not sure I can take the review request without access either. Yes I would file another bug for output flickering. Thanks again.
Comment 10•16 years ago
|
||
Fixed :)
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Attachment #355656 -
Attachment description: Patch for border issue → [checked-in] Patch for border issue
Attachment #355656 -
Flags: review?(mrogers)
Assignee | ||
Comment 11•16 years ago
|
||
Comment on attachment 355656 [details] [diff] [review] [checked-in] Patch for border issue Seems like we don't need the request any longer.
Assignee | ||
Comment 12•16 years ago
|
||
(In reply to comment #9) > sure I can take the review request without access either. Yes I would file > another bug for output flickering. Thanks again. Filed as bug 472453.
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•