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

This seems tautological for an event that doesn't bubble... I guess there's a bit I don't understand.

In [this scenario](https://flems.io/#0=N4IgZglgNgpgziAXAbVAOwIYFsZJAOgAsAXLKEAGhAGMB7NYmBvAHTQB4ATCANwAIInALwAFDACcmxAHxs+fMZIZy+XXgOEBhQtE6y08+dt0r2Aem4995y9Mog4MWNWIR6CRCADMiAIy+QAF8KdGxcT3wAKwQqOgYpPEUpfHoAB1oIeKVGcT4hPgAKGB4ASiFpOLhaWHwoWgBzAoByVIkpPikYcSaStjYkhhS0dMyc2AweGDzC4rKK92qYWobm1uy+ccmevrRjKE4hkazO3PyCueAVVObqHX2OrO20QLY9g7SMrM2ps4urm7unA2MAmMCegXsjmcrnceAAHH4AGxBEIgTA4PD4ahwGI0eiMZieSx8S4GPgAIww1AA1vVxLQAK5oTiIPgAYjAAAZOQAWADcbBeaDZA2IpPkhBgEHqJFZXk5qQAHgLnmw2W8SVdaHAIDC0KyMOSqlAGYwVRKpTLiKzfNylea+AB3QTEQg2u3KlQYNAQLAYPVyuAbTIg3K+IOZSA+xh8DBQHKYGNYWiTFVCtgAAWpMAAnmBxGEg8nJpqycRaCTiAW0HAoP6YKzOXwAEweoUQqhQmAuNw1vC2xBwoIAXUCQA), the child element is moving. If you 
- put the pointer on the path of the child and wait for it to overlap,
- move the pointer while remaining within bounds
- wait for the child to move away
- then move again

You'll get the `pointerleave` for both the child and the parent at the fourth step.

https://github.com/w3c/pointerevents/assets/54515/5f46fec3-b6a0-42db-9c6f-03abeeb77541

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.



-- 
GitHub Notification of comment by pygy
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/285#issuecomment-2010014348 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 16:37:02 UTC