Re: [pointerevents] Changing the DOM hierarchy while handling a "pointerenter" event produces significantly different results across browsers (#285)

What about the reparenting scenario ? As browsers work now the first parent isn't left, and the second isn't entered.

As an author, there are two kind of events I'd like to have access to:

- one set that matches those that govern the CSS :hover state
- one that reacts not only to pointer changes, but also to dynamic elements moving to the pointer (like the `dragenter`/`over`/`leave` do, but with the `over` hook that only fires when something has changed (`dragover` fires on a timer even if neither the pointer nor the element has moved, I suppose it has a purpose in the drag/drop scenario but this seems wasteful for a general handler).

In both cases, it would be ideal to get a guaranteed `pointerleave` guaranteed for each element that got a `pointerenter` when the element isn't in focus anymore.

-- 
GitHub Notification of comment by pygy
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/285#issuecomment-2016649166 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 24 March 2024 00:53:27 UTC