Re: [w3c/ServiceWorker] Confusion around new events after skipWaiting (#1295)

Yes I believe the spec intention is to keep sending functional events to the active worker.

To deal with the problem of never activating due to continuous events, Chrome implements a hard timeout of 5 minutes to let a "lame duck" worker continue being the active worker.

In theory this can also happen without skipWaiting: i.e., all clients are closed but the active worker keeps getting events somehow (e.g., lots of push messages).

-- 
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/1295#issuecomment-428600307