- From: Matt Falkenhagen <notifications@github.com>
- Date: Thu, 06 Jun 2019 21:16:04 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 7 June 2019 04:16:25 UTC
Hm, I think it doesn't actually work to make Run Service Worker blocking because then Terminate Service Worker can never be entered while the worker is starting up. It seems we have to make everything asynchronous or hand-wave that the user agent can abort starting the worker at any time. Or maybe keep it non-blocking and do something like: 1. Run the "Run Service Worker" algorithm. 1. In parallel: 1. Wait for service worker to be running or to have been aborted by the Terminate Service Worker algorithm. 1. If service worker is not running, return. 1. ... continue with dispatching the event etc. -- 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/pull/1419#issuecomment-499750869
Received on Friday, 7 June 2019 04:16:25 UTC