- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Sep 2021 17:01:19 +0000
- To: public-pointer-events@w3.org
I'm not sure if I'd go as far as it having an algorithm it has to follow, but I agree that developers should be able to work solely off of the coalesced events if they wish to work with coalesced events. The [following note](https://w3c.github.io/pointerevents/#coalesced-events:~:text=The%20PointerEvent's%20attributes%20will%20be%20initalized%20in%20a%20way%20that%20best%20represents%20the%20events%20in%20the%20coalesced%20events%20list.) in the spec suggests that the top-level event is a unified summary of the coalesced events: > The PointerEvent's attributes will be initalized in a way that best represents the events in the coalesced events list. In particular, this note is there to suggest that the movementX / movementY should reflect the total movementX / movementY of the coalesced events. However, it seems like this won't be strictly guaranteed given the point @NavidZ made that the top-level event could be resampled to the frame time. Considering resampling, I think we should still expect to see one real "raw" event in the coalesced events for each top-level move event. Perhaps we could say that the coalesced events should include all of the raw events which were included in the top-level event, even if none were coalesced? -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/409#issuecomment-915410695 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 September 2021 17:01:21 UTC