Re: [ServiceWorker] Race in Schedule Job algorithm handling of equivalent job promises (#853)

My initial gut feeling would be to explicitly handle the "update() call during install event" case and do case (a) for aggregation.  I'm not sure I like keeping state around just in case someone calls update().

I think case (a) is also closer to what devs might expect.  If I see a previous update() promise resolve, and then immediately call update() again, I think I would expect a second update process to run.

---
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/853#issuecomment-200921447