Bug 190313
| Summary: | Implement FetchEvent.resultingClientId | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Matt Falkenhagen <falken> |
| Component: | Service Workers | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ashley, ben, gsnedders, steffen.weber, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Matt Falkenhagen
This allows getting the client id before the client is created, for associating the fetch event for the main resource with fetch events for subsequent subresources.
Spec: https://w3c.github.io/ServiceWorker/#fetch-event-resultingclientid
WPT: https://github.com/web-platform-tests/wpt/blob/master/service-workers/service-worker/navigation-redirect.https.html
Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=778497
Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1264177
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ben Kelly
FWIW, this has been implemented in edge, firefox, and chrome now:
edge 18 already shipped in Oct
firefox 65 shipping end of January
chrome 72 shipping end of January
Just FYI since it might become more of an interop/compat issue.
Radar WebKit Bug Importer
<rdar://problem/89481601>
Sam Sneddon [:gsnedders]
This was done in bug 235070.
*** This bug has been marked as a duplicate of bug 235070 ***
Ashley Gullen
Please note the MDN docs still mark this as unsupported in Safari: https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent/resultingClientId
Sam Sneddon [:gsnedders]
(In reply to Ashley Gullen from comment #4)
> Please note the MDN docs still mark this as unsupported in Safari:
> https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent/resultingClientId
I'm aware; I came across this while preparing browser-compat-data updates for Safari 16 Beta!