Closed Bug 1538516 Opened 5 years ago Closed 5 years ago

Resolve the Promise returned by fetch() later during page loads

Categories

(Core :: DOM: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

Details

(Keywords: site-compat, Whiteboard: [necko-triaged])

Attachments

(2 files)

Similarly to bug 1538364.

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.

Priority: -- → P2
Whiteboard: [necko-triaged]

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.

Will there be studies for any of those changes?

Attached patch wip for testingSplinter Review

Just a patch for testing whether this could help with page loads.
(I think it does help with buzzfeed)

Keywords: site-compat
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
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Assignee: nobody → bugs
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: