- From: Jungkee Song <notifications@github.com>
- Date: Wed, 31 Jan 2018 07:22:32 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 31 January 2018 07:37:05 UTC
> I think Jake was pushing back (earlier in this thread) on preserving the last client-id across reloads I think what @jakearchibald said was preserving the *same* client-id across reloads wouldn't match the existing behavior in terms of the lifecycle of global objects/environments. > But if a page has access to the ID, it could push just that into the history, and then use it as part of a key into another storage mechanism before/after restore. This sounds interesting. Is the idea something like: - A client stores its history state keyed by the `id`. - The client's tab is discarded and restored. - The restored client looks up the history state using `discardedClientId`. > Probably discussed in the odd comment or two in various SW issues, though. https://github.com/w3c/ServiceWorker/issues/643 and https://github.com/w3c/ServiceWorker/issues/955. -- 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/1263#issuecomment-361845960
Received on Wednesday, 31 January 2018 07:37:05 UTC