Re: [pointerevents] Ensure predicted events only use input from the current partition (#518)

Thanks @patrickhlauke, you posted something very similar to what I have drafted from a slightly different perspective.  So posting anyway:

---

Does it help that the spec mentions two inputs to the prediction mechanism both of which are already "mostly exposed" to the Web?

> ... can make a prediction (based on past points, and the speed/trajectory of the movement) ...

The past points are known to the site already.  The speed/trajectory is mostly a function of the known rate of input events but I can see that the (unknown) shape of the stroke could have some role in the prediction too.  The shape may not be visible to the hardware or the browser predicting the next points, and even if it is visible, it seems to have a lighter role than the other already-known inputs.


-- 
GitHub Notification of comment by mustaqahmed
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/518#issuecomment-2332542888 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 5 September 2024 20:07:52 UTC