Re: [w3c/ServiceWorker] Clarification on what happens during a terminated activation (#1372)

For the time being Firefox/Gecko is planning to move to:
- Inhibit the "activate" event during shutdown, leaving the ServiceWorker in what amounts to its "activating" state where (relevant) functional events are delayed until the ServiceWorker becomes active.
- The next time a functional event is dispatched at the ServiceWorker, the "activate" will be dispatched.  As per the above, the (relevant) functional events will be enqueued until activation completes.
  - The general intent here is to conform to the behavior discussed around background fetch where a ServiceWorker will not be woken up if there isn't a controlled document involved.
  - For the quite common pinned-tab use-case this means that activation will happen when the browser next starts.
- No retries at this time, although I'll probably structure the metadata so this is possible.  (Since the choice is to have the activation happen at startup and thereby block page load, it would be undesirable to open the door to the page becoming permanently broken due to a very long-running activation that keeps being interrupted by the user restarting the browser in the hopes it will make the page load.)

-- 
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/1372#issuecomment-745438358