Re: [ServiceWorker] "Wait for all the tasks queued by Update State" language is problematic (#848)

So, I've thought about this some more and changed my mind.

I forgot that our "wait" language in the spec means an async wait.  So its not really blocking the main thread.

Also, we really should have consistent state change events even on workers.  So we really do need to wait for these.

I now wonder if we should have more "wait for state change events to fire" steps in the lifecycle steps.  For example, whenever we change the registration .installing, .waiting, and .active we may want to ensure all state change events have been flushed to content first.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/848#issuecomment-197371281