Re: [w3c/ServiceWorker] The promises returned by skipWaiting() should have more consistent activation-waiting behavior and not call Activate() multiple times (#1015)

> That said, I think it'd give more consistent and expected behavior to devs if skipWaiting() would resolve early even in the case that the state is "installed". Activate, of course, continues in parallel.

I agree this is the best thing to do now.

I think if we did everything again, I'd prefer it if `skipWaiting` always waited until the service worker became `activating`, but as @asutherland points out there's too much code out there using it in `waitUntil`, so it'll become a deadlock.

-- 
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/1015#issuecomment-263508737