Re: [pointerevents] Add new section explaining coalesced and predicted events (#364)

> A. In 5.1, the big text explanation right after getCoalescedEvents and getCoalescedEvents seems to belong to the new Section 11. Can we move the big text into it and add a link to the new section in each of getCoalescedEvents and getCoalescedEvents?

Yeah, I was considering this initially, but now wondering - should the new section here for coalesced/predicted events actually come under the (now renumbered) section 4 as a subsection, similar to 4.1.1 button states? and then yes, move the big text into it, here.

> B. The image about prediction needs to show the direction of drawing, otherwise it would be very confusing. Also, can we perhaps zoom in one part of the curve where we have two non-overlapping prediction-lines?

Agree about indication the movement direction that caused these points. Have to admit, because I was using it ended up being surprisingly difficult to "swoosh" a good representative gesture. I might have to tweak my source script and possibly just zoom in on the end of the gesture (where the predictions become a bit clearer/better than the often quite random predictions that Chrome seems to give me during a drawing operation currently).

> C. This is subjective, but in an introduction I prefer very focused code examples (no mousemove, maxTouchPoints, "keyboard events" etc).

fair point yes, especially since we already stress the need for considering keyboard etc elsewhere. will tweak

GitHub Notification of comment by patrickhlauke
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 22 April 2021 16:14:16 UTC