Re: [w3c/ServiceWorker] Central algorithm for updating service worker state and registrations (#1416)

I don't think these events fire enough to really worry about efficiency.  Its not a hot path.

I think we probably queue tasks this way because the spec used to be written that way and that influenced design decisions.  Reversing those design decisions might be costly, though.

Also, some of the existing tests may require some ordering that is not clearly defined in the spec.  To be honest at some point I was just trying to get the WPT tests to pass.

-- 
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/1416#issuecomment-498731797