Re: [w3c/ServiceWorker] Create F2F agenda - 7 November 2017 (#1206)

Client API and Navigate-hook
---
The latest agreement on FetchEvent (https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-311023682):
 - `clientId`: The client that initiates the request.
 - `resultingClientId`: The potentially-reserved client that will house the resulting document/worker.
 - `replacesClientId`: an existing client that will be replaced, or have its document replaced https://github.com/w3c/ServiceWorker/issues/1091#issuecomment-311325493

Proposal of not exposing reserved clients: #1216.

We are here now. I'd like to discuss:

- If the above meets the original use cases?
  - Per-client cache control.
  - ~~Messaging to reserved clients~~: this will be excluded by #1091.
- Will devs be happy?
- Implementable?
- How to write spec?
  - To spec the above, we should resolve https://github.com/whatwg/html/pull/2809#issuecomment-313374002 first.

Issues:
 - Client Id attributes and the initial about:blank case: #1091.
 - Not exposing reserved clients (#1216) may resolve #1034, #1035, #1215.
 - Navigate-hook: #765.
 - Redirected navigation: #1031.
 - Spec details: #1042.
 - Resolved (not closed yet): #1080, #1090.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1206#issuecomment-341664122