Closed Bug 1202597 Opened 9 years ago Closed 8 years ago

The order of RefreshDriver::Tick() for chrome and content is unpredictable

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Version:
Other Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1210261

People

(Reporter: hiro, Unassigned)

Details

In current implementation, the order of Tick on each vsync [1] is indefinite. I think root refresh driver should tick after all other refresh drivers ticked because the root refresh driver does DO a paint. 
 
[1] http://hg.mozilla.org/mozilla-central/file/5fe9ed3edd68/layout/base/nsRefreshDriver.cpp#l182
The order has been fixed in bug 1210261.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.