Re: [whatwg/dom] Nerfing all events on all event targets in a serviceworker after initial script evaluation seems odd (#371)

> or alternatively rephrase them with the suggestion to say something in the error console (and also only do it if the context object is the global object). Unfortunately whatwg/console#57 is still open.

@annevk, stating that in the spec would help. And a few more details about SW behavior:

> When it comes to functional events, we shouldn't spin up the service worker if it isn't in the set of event types to handle.

To make it clear, what do we want to do with the lifecycle events and the message event? I'm not thinking of adding the lifecycle events (install and activate) to this rule as Install and Activate steps change the service worker's state regardless of the existence of the event listeners.

> If that's the sticking point then I'm happy with us switching to a console warning for listeners attached to the global that service worker uses as lifecycle or functional events.

We may want to do this only for functional events I guess as Install and Activate are not checking the set of event types to handle.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/371#issuecomment-378476612