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

From: Hayato Ito <notifications@github.com>
Date: Mon, 20 Aug 2018 01:01:41 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/208/414231253@github.com>

> Remember, there are several mouseenter events per single mousemove if the subtree height > 1.

Ah, thank you for pointing that out. Please ignore my previous questions. I wrongly thought that `mouseenter` had a *similar* behavior to `mouseover`, regarding event dispatching.
[This](https://developer.mozilla.org/en-US/docs/Web/Events/mouseenter) explained well.

My previous questions are about the behavior of `mouseover`. That didn't apply to 'mouseenter' definitely.

I am now surprised that 'mouseenter' is dispatched on all ancestors! What a ridiculous... :(

Then, it sounds reasonable to make `mouseenter` composed events.
Compatibility-risk may comes if there is an `mousenter` event listeners for capturing-phase?


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

Received on Monday, 20 August 2018 08:02:04 UTC