Closed
Bug 1765777
Opened 3 years ago
Closed 3 years ago
NavigationPreload promise should be resolve while response available internal.
Categories
(Core :: DOM: Service Workers, defect, P1)
Core
DOM: Service Workers
Tracking
()
RESOLVED
FIXED
102 Branch
Tracking | Status | |
---|---|---|
firefox102 | --- | fixed |
People
(Reporter: edenchuang, Assigned: edenchuang)
Details
Attachments
(1 file)
To reduce the response latency, FetchEvent::PreloadResponse promise should be resolved while the response is available internally.
Assignee | ||
Updated•3 years ago
|
Assignee: nobody → echuang
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P1
Assignee | ||
Comment 1•3 years ago
|
||
In the previouse implementation, FetchEvent.preloadResponse is resolved when the response fetching finishes.
However, ServiceWorker respond letency could be increased since waiting for preloadResponse finishes.
The patch try to resolve FetchEvent.preloadResponse earlier when the response is available.
Pushed by echuang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b208cc31d00d
Resolve FetchEvent.preloadResponse when the response is available not the response end. r=dom-worker-reviewers,jesup.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox102:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•