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.

Yes, this is a much better idea!  It reduces the complexity and reduces skipWaiting() to its core.  As you describe it now, I understand that the current spec just wanted to ensure activation was initiated in the case the "Install" algorithm had already completed.  Currently step 24 of Install's "Wait until... registration's waiting worker's skip waiting flag is set." phrasing may cover this now?  Would the skipWaiting() description just provide a pointer/reference to that?

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