Re: [w3c/ServiceWorker] Feature request: Provide a way to delay execution of a new service worker (#1208)

Hi all,

I just wanted to say why I think some version of this proposal would have a _very_ positive impact on the future of the web:

1. Firstly, I agree with your reasoning behind preventing a Service Worker (SW) from blocking updates to itself _indefinitely_.  Unlike #822 and #761 , this proposal _does not_ suggest preventing SWs from being updated for a significant period of time (and certainly not indefinitely).

2. Many of us would _love_ to see the web become more trustworthy, at least for sites that choose to implement what @twiss is trying to enable.  By allowing web app creators to guarantee to users that they (the users) are not running a different, perhaps-malicious version of a web app than other users on the same site, and by being able to warn users when an unauthorized version of said web app's JavaScript is about to be executed, this greater trust can be achieved.

3. As a web developer, if I deploy a buggy SW, I want to be able to replace it quickly.  IIUC, the latest version of his proposal merely seeks to guarantee that a small window of time exists (e.g., 60 seconds) for the old SW to somehow warn the user that a possibly-malicious SW is about to replace it.

By providing this guarantee via the spec, you will enable a decades-long dream of web developers to come true -- for it to be possible to build web applications that are approximately _as trustworthy as native apps_, arguably more so, since web apps cannot run around on the user's hard drive to wreak havoc, but are instead trapped in the browser.

And for the majority of web apps who don't need such high security, they will remain unaffected.

Would love to see some version of this get accepted! :+1:

-- 
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/1208#issuecomment-432671146