- From: Jake Archibald <notifications@github.com>
- Date: Fri, 26 Jun 2020 08:21:05 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 June 2020 15:21:17 UTC
I guess I'm more thinking "I wonder if there was a good reason this wasn't done for shared worker". > Is there an alternative to solve Scott's use case of building a system to monitor service workers for unexpected errors? > Maybe firing on the service worker context onerror would be better and then let your own js logic route to the appropriate place. Hah, I was just typing something along those lines. -- 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/1519#issuecomment-650237315
Received on Friday, 26 June 2020 15:21:17 UTC