- From: Jungkee Song <notifications@github.com>
- Date: Wed, 13 Sep 2017 10:50:19 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 September 2017 10:50:54 UTC
> Should we instead change the skipWaiting() spec to effectively listen for a statechange event and resolve then? As commented in https://github.com/w3c/ServiceWorker/issues/1015#issuecomment-263508737, that change may create a deadlock to install handlers that waitiUntil the given skipWaiting promise. It seems we should keep the current behavior to not break the existing code. It should have been better if it returned void. -- 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-329131253
Received on Wednesday, 13 September 2017 10:50:54 UTC