Re: [w3c/ServiceWorker] What does it mean to wait "for a task to be executed (including its asynchronous steps)"? (#1109)

I added "including its asynchronous steps" to ensure the "wait for" step (step 6.8) is run after the navigate is completed as the [navigate](https://html.spec.whatwg.org/#navigate) algorithm returns in the step 11 and runs the process navigate fetch and process navigate response in parallel section.

With regard to the "wait for a task to be executed" language, I'd like to find a better way to do it. @annevk's [callback-style approach](https://fetch.spec.whatwg.org/#process-response) in fetch may apply generally? That is, a method creates a promise, queues a task and return the promise. The queued task queues callback steps back to the method caller's event loop when it's done. The callback steps resolve the promise.

-- 
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/1109#issuecomment-292885429