Re: [pointerevents] pointerout even if the pointer doesn't move? (#457)

The underlying [specification](https://w3c.github.io/pointerevents/#the-pointerout-event) states  "The user agent MUST [fire a pointer event](https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event) named [pointerout](https://w3c.github.io/pointerevents/#dfn-pointerout) when [[...]] The user agent has detected a scenario to [suppress a pointer event stream](https://w3c.github.io/pointerevents/#dfn-suppress-a-pointer-event-stream)."

I think we can agree that the test as written should satisfy the [clause](https://w3c.github.io/pointerevents/#suppressing-a-pointer-event-stream) "The user agent MUST suppress a pointer event stream when it detects that a pointer is unlikely to continue to produce events"

BUT this conflicts with the parent's [specification](https://w3c.github.io/pointerevents/#the-pointerout-event:~:text=it%20MUST%20not%20be%20fired%20until%20the%20pointing%20device%20has%20left%20the%20boundaries%20of%20the%20element%20and%20the%20boundaries%20of%20all%20of%20its%20descendants): "it MUST not be fired until the pointing device has left the boundaries of the element and the boundaries of all of its descendants"

Perhaps we should add language to clarify this?  Perhaps something like: "it MUST not be fired while the pointing device remains un-moved within the previous boundaries  of the element and the boundaries of all of its descendants.  Note that this boundary test should consider the position of elements at the time of the originating event."


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


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

Received on Monday, 13 May 2024 14:55:12 UTC