[pointerevents] Considering adding an API to get pre-coalesced points

RByers has just created a new issue for 
https://github.com/w3c/pointerevents:

== Considering adding an API to get pre-coalesced points ==
When a web app is slow, most browsers will coalesces multiple movement
 events into a single one (with the latest position only).  This is 
perfect for scenarios that care most about minimizing latency, but 
unfortunate for scenarios (like art applications) where maximum motion
 detail is required.  Similarly, many OSes will artificially align 
input to v-sync for maximum motion smoothness, but for drawing 
scenarios it's really the raw points the app wants.

Android 
[MotionEvents](http://developer.android.com/reference/android/view/MotionEvent.html)
 are similarly batched and expose a history API (eg. 
[getHistoricalX](http://developer.android.com/reference/android/view/MotionEvent.html#getHistoricalX(int,
 int))) to get all the original raw points.  iOS 9 adds a 
`coalescedTouchesForTouch` API for this ([sample 
code](https://developer.apple.com/library/prerelease/ios/samplecode/TouchCanvas/Listings/TouchCanvas_CanvasView_swift.html#//apple_ref/doc/uid/TP40016561-TouchCanvas_CanvasView_swift-DontLinkElementID_6)).

Perhaps `PointerEvent` should have a similar API?  Eg. 
`getCoalescedEvents` that returns an array of `PointerEvent` instances
 for the same pointerId?

I don't think this is particularly urgent (the art scenarios are 
fairly niche), but may become so if we want to block #9 on this.

See https://github.com/w3c/pointerevents/issues/22

Received on Friday, 18 September 2015 15:12:00 UTC