Re: [w3c/ServiceWorker] resurrected service workers don't fire an activate event which may break expectations (#1204)

F2F: `resurrection` event instead? It's a hook for developers to read about.

Currently in the spec, if you unregister the SW, then reregister with a different URL, if that fetch fails the registration is resurrected. New clients will be controlled by the reg while the script is fetching.

`resurrection` must happen on the active worker, regardless of script URL changes.

We're not really happy with any of these ideas.

Action: @jakearchibald to write a blog post asking developer on expected behaviour.

-- 
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/1204#issuecomment-342595330