Re: [whatwg/dom] addEventListener defer option to call that handler after all other handlers run (#730)

Do you mean if they add the same callback function *or* if they bind to the "deferred phase" for the same event?  I presume it's the latter, but just in case, I would expect the former to just ignore the call since the callback already exists within the set of callbacks attached to that event for the deferred phase.  In the case of the consumer binding their own functions to an event in the deferred phase, for which a behaviour has already attached an event, I guess it would call the callbacks in the order that they were added, as is the case for the capturing and bubbling phases.

I did almost call out this potential issue in my original post, but I'm not sure if it's really an issue, and that we couldn't just make it clear in documentation that the deferred phase isn't intended for the majority of consumer event handlers.  Maybe that wouldn't stop it from being misused, 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/730#issuecomment-456141614