Re: [w3c/ServiceWorker] should `ServiceWorker` interface implement `AbstractWorker` mixin? (#1268)

It seems shared workers handle only the errors that the script fetching fails or the caller of the constructor is a non-secure context. That is, they ignore other runtime script errors.

I think we can add the runtime script errors section in Run Service Worker that just goes up to (and not firing `error` to `ServiceWorker`):
> If the error is still not handled afterwards, the error may be reported to a developer console.

and stop including `AbstractWorker`.

-- 
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/1268#issuecomment-362222131