- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 16:34:26 +0000
- To: public-pointer-events@w3.org
I've updated the test to also listen for events on the ancestor elements of the removed target. This allowed my to verify that after the removal chrome and safari fire pointer events at the current hit test target. Further, the implicit capture is gone so the target can change as the touch moves over other elements. > Tested on Android and Chrome fires some pointermoves (that 'some' part is really confusing) and then stops firing them Strange in my testing there were no pointermoves fired to the removed target. Pointermove is only fired at the parent. > but keeps firing touchmoves. Firefox just fires the initial event and stops there. I wonder what Safari does. I tested Safari and found it to be consistent with Chrome. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/486#issuecomment-1758076805 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 16:34:27 UTC