- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 May 2021 14:34:20 +0000
- To: public-pointer-events@w3.org
> I think I agree. That movementX/Y example does feel a bit odd. It makes sense to me. It's trying to say that you don't need to pay attention to the coalesced event list because the top-level events will capture what has happened. I.e. movementX/Y should be the movement since the last top-level event that you would have seen sent to your event handler, not the movement since the previous internal coalesced event. > (And does some browser actually do that?) Yes. Try https://jsbin.com/dofojij/edit?html,js,output on chrome. You'll see when there are coalesced events, that the movementX/Y of the main event is the sum of the movement of the coalesced events. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/374#issuecomment-848821580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 May 2021 14:34:22 UTC