Re: [w3c/ServiceWorker] There should be no such thing as "fail to activate" (#659)

Thanks, I do see that the promise could be extended to try as much again (assuming a timeout doesn't win out). But what of the issue with messaging from the app into the worker (before a timeout stops it)?

I am currently passing in info from my library users' files (already cached during `install`) which I am reading into IndexedDB during the activation phase, but if the user closes their tabs, e.g., during the waiting phase, there may be no other code of mine left running which can pass in the dependency file info so that the activation in the worker can complete so that it is available next time the user loads my site.

And the impression I get is that I can't store this in a variable during the install phase such that it will be available during the activation. Would I have to create a separate database to share this state persistently?

-- 
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/659#issuecomment-384932931