#307: FetchEvent.resultingClientId
Discussions
2019-06-19
Dan: needs eplainer.. been sitting around for a while.
Sangwhan: needs new assignees.
2019-06-26
Sangwhan: we need to close this as well as we haven't provided feedback and it has shipped in the meanwhile.
Peter: "overtaken by events"
Peter: how many implementations?
Sangwhan: as of today it's 2.
[conesnsus to close
OpenedOct 1, 2018
Bonjour TAG,
I'm requesting a TAG review of:
Name: FetchEvent.resultingClientId
Specification URL: https://w3c.github.io/ServiceWorker/#fetch-event-resultingclientid
Explainer, Requirements Doc, or Example code: There's some discussion at https://github.com/w3c/ServiceWorker/issues/1091 and https://github.com/w3c/ServiceWorker/issues/1245.
Tests: service-workers/service-worker/navigation-redirect.https.html
Primary contacts: @mattto @jungkees @jakearchibald
Further details (optional):
You should also know that...
There is a related
replacesClientId
attribute specified, which I am not planning to implement in Chrome for now because there has been no clear developer demand.We'd prefer the TAG provide feedback as (please select one):