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

> Over a discussion, we'd setteled on the current behavior

I don't really see a discussion.  I see @jakearchibald asserting that this should be the behavior and no one questioning it, or thinking about how it ties in to other specifications.  For example, it introduced inconsistent behavior between `addEventListener("fetch", ...)` and setting `onfetch`...

> SW lifecycle events plus all other functional events including fetch, push and future extesions are within the scope of this behavior

OK, but you're doing this for _all_ events, including random made-up ones the service worker script itself decides to fire.  I don't see why this is at all reasonable.

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