Re: [w3c/ServiceWorker] skipWaiting() promise should resolve after promotion to .active (#1187)

We already have a deadlock scenario:
1. A registration is created and has its active worker.
2. Clients navigate to the scope and start being controlled.
3. A new service worker version with no `skipWaiting()` call is installed (and not promoted due to the open controlled clients).
(The user does not close the tabs for days and come back.)
4. A new service worker version with `waitUntil(skipWaiting())` call in the install handler is installing.

Should we make it "just resolve immediately always" as @mattto suggested?

-- 
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/1187#issuecomment-398593294