Re: [w3c/ServiceWorker] Service Workers are too hard to clean-up (Issue #1695)

bes left a comment (w3c/ServiceWorker#1695)

I want to add another data point: Service-worker deregistration is fall-forward only currently. If I deploy my site with a service worker, but I need to roll-back the site for some reason; bugs, security issues, whatever, then the only option I have is to fall-forward by publishing a site with a service worker on it (it can be empty, that's besides the point).

My point is: Rolling back after publishing a site with a service worker will make the site unusable, or at least that is my experience - the site just reloads ad infinitum until I open the dev tools and nuke the service worker.

This is a bad default. No service worker file should mean automatic unregister & clean up in my opinion. Having service workers around after the service-worker file is gone because some sites can't get their act together is a weird choice.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1695#issuecomment-4461382945
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1695/4461382945@github.com>