Re: [whatwg/dom] Reset dispatching flags when retargeting to a different target than event's (#402)

Before that new behaviour was introduced, there was not a single code path when dispatching an event that wouldn't clear these flags, even when no listener has actually been invoked. I feel like this property of the algorithm should be preserved.

-- 
Anthony Ramine

> Le 24 janv. 2017 à 09:30, Anne van Kesteren <notifications@github.com> a écrit :
> 
> That is true. I guess the question is whether you expect those to be always unset even if the event didn't really end up dispatching. (The main reason they're unset at the end is because listeners might have set them.)
> 
> I don't think it matters much what we do since this is new behavior. So we get to decide what makes sense for this edge case (and write tests for it).
> 
> I kinda like @hayatoito's fix since it's simple, but I'm willing to go for the alternative if there's a good reason.
> 
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


-- 
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/pull/402#issuecomment-274741446