Re: [w3c/ServiceWorker] Clarification on what happens during a terminated activation (#1372)

👋 from the Workbox team.

We just [ran into](https://github.com/GoogleChrome/workbox/issues/1783) what looks to be someone running into inconsistent cache states due to Firefox failing activation (for reasons unknown) causing the service worker to re-install. Workbox currently should play nicely with Chrome's current behavior around a failed activation (re-firing the `activate` event) and now that we're aware that it's an issue, we can also adapt to Firefox's current behavior (starting from scratch with a new `install` event).

What I'm concerned about is that I'm not sure how we can deal with Edge's current behavior of not re-firing either `activate` or `install` (followed by `activate`), especially since it sounds like that's the "correct" behavior that might be standardized. If Edge's behavior were implemented everywhere, would we just have to check for temporary cache entries that need to be cleaned up each time the service worker starts up?

-- 
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-446766388