Re: [w3c/ServiceWorker] Error handling inconsistent with other Workers (#1519)

Ah wait, I misread this. For a while we had an unused `onerror` endpoint in the spec, but we got rid of it ages ago.

We don't really define `ServiceWorker.onerror`, we just get it from `AbstractWorker`. Our behaviour here is the same as [shared workers](https://html.spec.whatwg.org/multipage/workers.html#runtime-script-errors-2), but that doesn't mean it's great.

The problem is that there's a 1-1 relationship between dedicated workers and `Worker` instances. With shared/service workers, an error event would be more of a broadcast, and it isn't clear if that's a good thing.

-- 
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-650059192