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

> there's the question of why we're doing it at all too

It had started by https://github.com/w3c/ServiceWorker/issues/718#issue-92573396 to deterministically detect whether no event handler's registered for a given event (to reduce unnecessary SW start-up delay in such cases.) Over a discussion, we'd setteled on the current behavior. (TL;DR see https://github.com/w3c/ServiceWorker/issues/718#issuecomment-173830892 and below.)

> Why are we doing this for all event targets?

I think this was a miss. This should be only for the events on ServiceWorkerGlobalScope not for all the EventTargets.

> Why are we even doing it for all events?

Given that it should be only for ServiceWorkerGlobalScope, SW lifecycle events plus all other functional events including fetch, push and future extesions are within the scope of this behavior.

> handling this like upload events on XHR.

Could you give me a pointer or explain a bit more on this?

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