- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Sep 2024 20:53:00 +0000
- To: public-pointer-events@w3.org
mustaqahmed has just created a new issue for https://github.com/w3c/pointerevents: == [PointerEvent algorithms] == The UIEvents spec assumes there is "almost" a 1:1 correspondence between mouseenter and pointerenter (and same for other boundary events: mouseleave, mouseover, mouseout). For example, Step 4.1.4 in [UIEvents Section 3.4.3.15. handle native mouse move](https://w3c.github.io/uievents/#handle-native-mouse-move-id) says “maybe send pointerenter event with mouseenter” where the “maybe” is vague and yet it is unable to cover the underlying complexity with multiple pointers. ### Possible solution Solve #519 (Order of boundary events) first, then link the corresponding algorithms in UIEvents and PointerEvents through [PE Section 11.1 Tracking the effective position of the legacy mouse pointer](https://w3c.github.io/pointerevents/#dfn-tracking-the-effective-position-of-the-legacy-mouse-pointer). Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/520 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:53:01 UTC