190313 2018-10-05 08:23:05 -0700 Implement FetchEvent.resultingClientId 2022-06-06 14:50:16 -0700 1 1 1 Unclassified WebKit Service Workers WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 235070 InRadar P2 Normal --- 1 falken webkit-unassigned ashley ben gsnedders steffen.weber webkit-bug-importer youennf oldest_to_newest 1466692 0 falken 2018-10-05 08:23:05 -0700 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 1488425 1 ben 2018-12-17 06:26:58 -0800 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. 1846080 2 webkit-bug-importer 2022-02-25 10:35:57 -0800 <rdar://problem/89481601> 1874286 3 gsnedders 2022-06-06 06:38:32 -0700 This was done in bug 235070. *** This bug has been marked as a duplicate of bug 235070 *** 1874305 4 ashley 2022-06-06 07:55:19 -0700 Please note the MDN docs still mark this as unsupported in Safari: https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent/resultingClientId 1874376 5 gsnedders 2022-06-06 14:50:16 -0700 (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!