Re: Requirements for PE v2

Of all the things we've discussed over the years, the one I personally
think is highest priority is:

API for requesting high-frequency movement position data. See
http://lists.w3.org/Archives/Public/public-pointer-events/2014AprJun/0055.html

This is now tracked in https://github.com/w3c/pointerevents/issues/22
("Considering adding an API to get pre-coalesced points").

Anecdotally this seems pretty important for drawing scenarios (especially
pen), and is something all native platforms (Windows, Android, and most
recently iOS) have APIs for.  This is something I think we might be
interested in including in Chrome sooner rather than later.  Thoughts?

Rick

On Sat, May 14, 2016 at 4:07 AM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> More for general interest, I guess, but: some wishes/ideas for v2 that the
> group put together back in Dec 2014
> https://www.w3.org/wiki/PointerEvents/UseCasesAndRequirements#Requirements:_Pointer_Events_v.Next_Specification
>
> Maybe worth having a look if there's anything we wanted to at some point
> and lost track of? Though I guess many of the issues/ideas have since been
> superceded.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>