Re: [w3c/ServiceWorker] Missing task queuing (#1403)

Yes my intent was that Update would block until the callback is run with the result of starting the service worker.

For postMessage(), doesn't it still make sense to wait for the service worker to have started before continuing? I.e., the service worker's global object must be set for the postMessage() steps to work.

I'm guessing we want Run Service Worker to block until the service worker starts (just before "Run the responsible event loop" is called) and return the evaluation status. Is there a rigorous way to specify that?

Something like:

Run Service Worker:

3. Let `evaluationStatus` be null.
4. Create a separate parallel execution environment (i.e. a separate thread or process or equivalent construct), and run the following substeps in that context in parallel:
4.1. Setup the service worker...
 ...
4.14. Set `evaluationStatus` to status.
4.15. Run the responsible event loop...
5. Wait for `evaluationStatus` to be set.
6. Return `evaluationStatus`.

-- 
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/1403#issuecomment-494629387