Re: [ServiceWorker] should installing workers be persisted if browser is killed? (#794)

> could we have a section like "Browser Shutdown" that says which of installing/waiting/active get discarded and which get persisted to next browser start?

Agreed.

> Chrome's position is that when the browser is closed, the .active worker no longer controls a client. So it restarts with only the .waiting worker which is activated on the next fetch or push event.

I think the next fetch when the browser restarts will not activate the .waiting. The fetch just falls back to the network. (There's no active worker to dispatch fetch event at, so it doesn't get a chance to invoke Soft Update either.) So, making "Browser Shutdown" invoke Activate for all the registrations having both .active and .waiting makes sense? Let me know if this conforms to the current Chrome behavior.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/794#issuecomment-161485059