- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Mar 2024 19:03:50 +0000
- To: public-pointer-events@w3.org
> This seems tautological for an event that doesn't bubble... Yikes, in my last post I meant to say non-bubbling `pointerover` and `pointerout` events to infer the "hover" state 😞. > In the child removal scenario example I suppose that the browser doesn't send the event to the child because it's been detached, but I don't get why the parent is not notified. Yes, thanks, your repro is another way to look at the same problem we discussed above: in "q2" [here](https://github.com/w3c/pointerevents/issues/285#issuecomment-832235942) we have an extra `pointerenter` because the hovering pointer causes the second `pointerenter` as if the first one is "forgotten", and your repro isolates the first one. According to [the spec](https://w3c.github.io/uievents/#event-type-mouseenter:~:text=A%20user%20agent%20MUST%20dispatch%20this%20event%20when%20a%20pointing%20device%20is%20moved%20off%20of%20the%20boundaries%20of%20an%20element%20and%20all%20of%20its%20descendent%20elements) this seems working as intended because "the pointer didn't move off from an (existing) element" through the deletion. But the pairing mismatch question remains unresolved here unfortunately. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/285#issuecomment-2010391049 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 March 2024 19:03:51 UTC