- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Nov 2024 18:07:48 +0000
- To: public-pointer-events@w3.org
> We still need to discuss 4-5. I think point 5 is just a bug, do you think there's any reason it should behave differently? For point 4, I think it would be better not to dispatch move events if the pointer hasn't physically moved. This to me feels like it more directly reflects what has happened - the pointer hasn't moved but it is over a new element. If we dispatched move events, then I would expect that you'd see move events even if the element that it's over didn't change. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/529#issuecomment-2504519010 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 November 2024 18:07:49 UTC