Re: [whatwg/dom] Shadow: Update the behavior of event dispatch when target and related… (#336)

Yeah, I am fully aware of that. The point is *UA events*.  There is a case where we should not dispatch a UA event. Could you have a chance to see the example in https://github.com/whatwg/dom/pull/336#issue-180583922?

Maybe https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/fast/dom/shadow/shadow-boundary-events.html?l=150 might be helpful to understand the case. In this case, we should not dispatch an mouseover event on the shadow host (shadowF).

That is the motivation of this change. If we are to dispatch a *synthetic* event which has the same condition (the same target (shadowF) and the same relatedTarget (shadowI)), and want to make sure that event is dispatched,  we have to check whether an event is a synthetic event or not. I do not want to introduce the divergence between synthetic events and UA events in order to address this very minor case.




-- 
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/336#issuecomment-251063191