Re: [w3c/uievents] Consider to make mouseenter/leave (and pointerenter/leave) uncomposed (#208) from Hayato Ito on 2018-08-22 (public-webapps-github@w3.org from August 2018)

From: Hayato Ito <notifications@github.com>
Date: Tue, 21 Aug 2018 19:07:03 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/208/414883044@github.com>

Thanks.
I confirmed that Blink fires `mouseenter` events on all shadow-including descendants, [B, C, shadow-root1, D, E, shadow-root-2, F, G], for the case 1. I confirmed that using https://jsfiddle.net/eu1pn7Lx/21/.

I also found that it is difficult to tell how `mouseenter` event's relatedtarget is set there. :(
Thus, it could happen that a shadow host can receive more than one `mouseenter` at TARGET phase.

Given that UA already fires `mouseenter` events on all shadow-including descendants, I support to make *enter/*leave event non-composed.


-- 
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-414883044

Received on Wednesday, 22 August 2018 02:07:25 UTC