Re: [slightlyoff/ServiceWorker] More clarity around waiting for an active worker to finish (#916)

OK here's roughly what I plan to start implementing to fix the Chrome bug:
- The waiting worker gets promoted to active once there are no controllees and the incumbent worker has no in-flight events (fetch/sync/push etc). 
- When a page closes, we expect its related network requests to get cancelled, so outstanding fetch events should not block activation when there are no controllees.
- skipWaiting bypasses the no controllees requirement, but we still wait until there are no in-flight events (optionally we might decrease the event timeout).
- As usual, incoming fetch/sync/push events always go to the active worker.

---
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/916#issuecomment-228306560