Closed
Bug 1521786
Opened 6 years ago
Closed 6 years ago
Keep RefreshDriver ticking before first contentful paint
Categories
(Core :: Layout, enhancement, P2)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
(Blocks 3 open bugs)
Details
Attachments
(1 file)
|
(deleted),
patch
|
farre
:
review+
|
Details | Diff | Splinter Review |
Keep RefreshDriver ticking before first contentful paint so that we can avoid the latency from re-starting it and can try to paint as soon as possible.
This way there will be pending vsync messages more often and we can for example yield before running slow scripts.
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Comment 2•6 years ago
|
||
Comment on attachment 9038354 [details] [diff] [review]
keep_refreshdriver_running.diff
This kind of opposite to the other patch. We do want to get the first contentful paint asap, so better to keep driver up and running. 4s is "educated guess".
Attachment #9038354 -
Flags: review?(afarre)
|
||
Comment 3•6 years ago
|
||
Comment on attachment 9038354 [details] [diff] [review]
keep_refreshdriver_running.diff
Review of attachment 9038354 [details] [diff] [review]:
-----------------------------------------------------------------
Same thing here, we could easily have prefs for constants here, but I'm ok with not having them.
Attachment #9038354 -
Flags: review?(afarre) → review+
|
||
Updated•6 years ago
|
Priority: -- → P2
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6c77b51f59e0
Keep RefreshDriver ticking before first contentful paint, r=farre
|
||
Comment 5•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in
before you can comment on or make changes to this bug.
Description
•