Re: [w3c/uievents] Consider to make mouseenter/leave (and pointerenter/leave) uncomposed (#208)

@smaug---- : Hm... I still don't understand what the exact compat. issues with EA sites are.

Is it that the site breaks if the shadow host gets two `mouseenter` / `mouseleave` events? Or if shadow tree and shadow host get two independent `mouseenter` / `mouseleave` events?

If the issue is that the host shouldn't get two `mouseenter` events, that's understandable because th whole point of `mouseenter` is that it should be dispatched once on an element as the pointing device enters the element.

@hayatoito : I don't think this would break anything as long as we continue to dispatch `mouseenter` / `mouseleave` on the shadow host. Because `mouseenter` / `mouseleave` don't bubble and instead be dispatched on each element the pointing device enters, each element in the flat tree is independently informed of the pointing device's move. This is in contrast with other pointing device events such as `mousemove`, which is dispatched on the leaf node inside which the pointing device movement is detected, and the way ancestor elements detects this is by observing the event bubbling up to them.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/208#issuecomment-413776262