Resolve the Promise returned by fetch() later during page loads
Categories
(Core :: DOM: Networking, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
(Keywords: site-compat, Whiteboard: [necko-triaged])
Attachments
(2 files)
1.61 KB,
patch
|
Details | Diff | Splinter Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Similarly to bug 1538364.
Comment 1•5 years ago
|
||
Just FYI, if the fetch() delivers a "highly visible content" *), or is on the path to deliver it to the screen, it may actually lead to a regression in perceived load perf.
*) highly visible content = e.g. a large image in the middle of the screen, a featured image of an article, a dynamic gallery...
I was struck by that few times when I was tuning the tailing feature and why I made the delay to keep tailed requests queued way shorter after domcontentloaded event.
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Sure. This is a tricky case. But as bug 1538364 hints, and bug 1270059 too, using idle-or-right-after-load approach may help quite a bit in certain cases.
Comment 3•5 years ago
|
||
Will there be studies for any of those changes?
Assignee | ||
Comment 4•5 years ago
|
||
Just a patch for testing whether this could help with page loads.
(I think it does help with buzzfeed)
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
The patch depends on https://bugzilla.mozilla.org/show_bug.cgi?id=1558215
Depends on D34366
Assignee | ||
Comment 7•5 years ago
|
||
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7ba9d3d60a93 Resolve the Promise returned by fetch() later during page loads, r=baku
Comment 9•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 10•5 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.dev/en-CA/docs/2019/resolving-promise-returned-by-fetch-is-now-deferred-during-page-load/
Description
•