Closed
Bug 786476
Opened 12 years ago
Closed 12 years ago
Background tabs cause multiple whole window repaints
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
DUPLICATE
of bug 786484
People
(Reporter: taras.mozilla, Unassigned)
Details
(Whiteboard: [Snappy])
1.Turn on nglayout.debug.paint_flashing pref. 2. Load a page in a background tab 3. Observe foreground tab & rest of window repaint twice once page finishes loading. I guess this has something to do with tab reflows
Comment 1•12 years ago
|
||
I wasn't able to reproduce this on Linux, Windows XP, or Mac.
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Timothy Nikkel (:tn) from comment #1) > I wasn't able to reproduce this on Linux, Windows XP, or Mac. Thanks for trying. I tried a build with a clean profile. It does not exhibit this behavior. I'm going to keep narrowing down differences between the two profiles until I figure this out.
Comment 3•12 years ago
|
||
We specifically kill invalidates that come from inside background tabs, so if this was happening it would be very interesting.
Reporter | ||
Comment 4•12 years ago
|
||
Narrowed this down to browser.newtab.preload being set to true in my profile.
Depends on: 753448
Comment 5•12 years ago
|
||
I can reproduce this on Mac. Setting the "busy" attribute on the tab is what causes the repaint - removing the attribute doesn't cause another repaint. This only happens if new tab preloading is enabled. Theory: the hidden iframe in the window is causing us to unnecessarily repaint the whole window when certain chrome style changes occur.
OS: Windows 7 → All
Hardware: x86_64 → All
Comment 6•12 years ago
|
||
The browser is inserted into browser-panel, and hidden by setting .collapsed = true: http://hg.mozilla.org/mozilla-central/annotate/6e78c3efd115/browser/modules/BrowserNewTabPreloader.jsm#l88
Updated•12 years ago
|
Comment 7•12 years ago
|
||
(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #5) > I can reproduce this on Mac. Setting the "busy" attribute on the tab is what > causes the repaint - removing the attribute doesn't cause another repaint. > This only happens if new tab preloading is enabled. > > Theory: the hidden iframe in the window is causing us to unnecessarily > repaint the whole window when certain chrome style changes occur. So this is essentially a duplicate of bug 786484.
Updated•12 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•