- From: Ben Kelly <notifications@github.com>
- Date: Fri, 01 Sep 2017 13:41:35 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 1 September 2017 13:43:33 UTC
I think a series of spec changes have changed skipWaiting() indirectly. I agree the current spec says that skipWaiting() should resolve before the worker state is updated, but is that the intent of this promise? Should we instead change the skipWaiting() spec to effectively listen for a statechange event and resolve then? @jakearchibald @jungkees what do you think? -- 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-326582954
Received on Friday, 1 September 2017 13:43:33 UTC