- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 21:48:47 +0000
- To: public-pointer-events@w3.org
We discussed this today and came to the following rough plan of action: 1. Fire mousedown (and other compat mouse events) to the still attached ancestor. This ensures that ancestor listeners still see the events that they would expect to see. 2. Use the common ancestor of the pointerdown and pointerup events to target the click event - this will make it so that the above change does not result in click being fired on element removal during the pointerdown. 3. Remember the element targeted by the pointerdown even if it is removed from the DOM. This supports re-ordering DOM cases like [crbug.com/1367190](https://bugs.chromium.org/p/chromium/issues/detail?id=1367190) as we remember the original target before the reordering happened. The behavior is consistent with if you changed the position on down but the user moved their mouse to again be over the same element. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/492#issuecomment-1823553102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 21:48:49 UTC