- From: Mustaq Ahmed <notifications@github.com>
- Date: Tue, 17 Sep 2024 13:39:57 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 17 September 2024 20:40:01 UTC
Mouse boundary event (mouseenter/leave/over/out) dispatch is currently tracked using the state variable [`last_mouse_element`](https://w3c.github.io/uievents/#last-mouse-element). The variable is checked and updated only in [Section 3.4.3.15](https://w3c.github.io/uievents/#handle-native-mouse-move-id) (handle native mouse move). Native mousedown and mouseup events should check and update the variable too: a mousedown always follows a mouseenter and mouseover to the same target in all major browsers. ### Possible solution Make a method `updateElementUnderMouse` that checks and updates the variable and fires all required boundary events. Call this from native mouse event handlers. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/383 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/383@github.com>
Received on Tuesday, 17 September 2024 20:40:01 UTC