RESOLVED DUPLICATE of bug 235070 190313
Implement FetchEvent.resultingClientId 
https://bugs.webkit.org/show_bug.cgi?id=190313
Summary Implement FetchEvent.resultingClientId
Matt Falkenhagen
Reported Friday, October 5, 2018 4:23:05 PM UTC
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
Comment 1 Monday, December 17, 2018 2:26:58 PM UTC
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
Comment 2 Friday, February 25, 2022 6:35:57 PM UTC
<rdar://problem/89481601>
Sam Sneddon [:gsnedders]
Comment 3 Monday, June 6, 2022 2:38:32 PM UTC
This was done in bug 235070. *** This bug has been marked as a duplicate of bug 235070 ***
Ashley Gullen
Comment 4 Monday, June 6, 2022 3:55:19 PM UTC
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]
Comment 5 Monday, June 6, 2022 10:50:16 PM UTC
(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!
Note You need to log in before you can comment on or make changes to this bug.