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

Sounds good to me to remove resurrection. It causes complexity in the code and I doubt sites are relying on it.

I was briefly worried you'd get into situations where getRegistration() can return a registration that doesn't have your controller in it, but I think that's already possible today. For example, you can unregister then register a new registration with a longer matching scope.

When making the spec change for this, we'd want to update and review unregister-then-register.https.html and unregister-then-register-new-script.https.html.


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