Re: [w3c/ServiceWorker] Spec how extendable events are given time to execute (#1566)

I don't have a problem with short lived, closed if no tab is open, stateless service workers and certainly don't object to the browser killing runaway service workers but Chrome implemented Server Sent Events in Service Workers and then have made them unusable by killing the service worker immediately after an event and not waking it up for subsequent events.

There needs to be a way to either extend the life span or restart service workers for server sent events and similar external events supported by service workers.


-- 
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/1566#issuecomment-958095193