- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Sep 2024 20:47:27 +0000
- To: public-pointer-events@w3.org
mustaqahmed has just created a new issue for https://github.com/w3c/pointerevents: == [PointerEvent algorithms] Order of boundary events == When the mouse pointer moves from element A to element B, how does a browser determine the sequence of boundary events (enter, leave, over, out) to fire? ### Problem PointerEvents boundary event (enter, leave, over, out) dispatch is not defined, and the corresponding dispatch mechanism in UIEvents [Section 3.4.4. Mouse Event Order](https://w3c.github.io/uievents/#events-mouseevent-event-order) is example-based without a precise definition text. ### Possible solution Fix https://github.com/w3c/uievents/issues/383, then override that in PointerEvents into three different methods (one per pointer type) each with a corresponding state for "element under current primary pointer". Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/519 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 September 2024 20:47:27 UTC