- From: Joseph Liccini <notifications@github.com>
- Date: Tue, 04 Dec 2018 10:17:40 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 December 2018 18:18:01 UTC
I agree with @wanderview -- the isue is the unexpected partial state. For a concrete example, let's consider the Workbox precaching activation flow. During installation, the assets are downloaded into a 'temp' cache. During activation, the assets are transferred from the 'temp' cache into the 'active' cache. A workbox service worker only serves assets from the 'active' cache. If activation does not fully complete, but we move the worker into the active slot, some assets will be un-servable from the 'active' cache, because they did not complete moving from the 'temp' cache. It would mean that all 'activate' handlers need to be built in a way that is compatible with a partial, non-deterministic completion point. This is possible, but needs to be clearly documented in the spec -- 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/1372#issuecomment-444202222
Received on Tuesday, 4 December 2018 18:18:01 UTC