Re: [whatwg/dom] Allow an EventTarget to provide the default value of the AddEventListenerOptions (#365)

This seems reasonable to me.

> Instead of making the event target the extension point and passing the event type, make the event type the extension point and pass the event target.

I can see how this might be simpler.

> Resolve undefined to true or false later when determining which elements have event handlers that can preventDefault() and block scrolling.

This would have slightly different semantics from the current definition, eg. in the case that a 2nd HTMLBodyElement is added after the `addEventListener` call.  We could probably work around that, but in general deferring the decision point to after `addEventListener` seems more complex and harder to reason about to me.  I don't have a strong opinion though.

-- 
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/365#issuecomment-259543370

Received on Wednesday, 9 November 2016 22:20:27 UTC