Re: [DOM3Events] InputDevice API sketch

I've created a more formal proposal for an initial simple InputDevice API
<http://rbyers.github.io/InputDevice/inputdevice.html> (though probably
still sloppy by W3C spec standards).  Please provide any additional
feedback you have on it, ideally as GitHub issues
<https://github.com/RByers/InputDevice/issues> (or feel free to submit pull
requests, eg. for editorial improvements).

The respository <https://github.com/RByers/InputDevice/> contains a polyfill
<https://github.com/RByers/InputDevice/blob/gh-pages/inputdevice-polyfill.js>
and
a number of tests <http://rbyers.github.io/InputDevice/tests/>.  We're
nearly done implementing
<https://code.google.com/p/chromium/issues/detail?id=476530> this API in
blink and hope to ship it soon.

Thanks,
   Rick

On Sat, Mar 28, 2015 at 7:38 PM, Rick Byers <rbyers@chromium.org> wrote:

> Thank you very much!
>
> So what's the best path forward to starting to spec something here?  Is
> the UI Events spec the best place to put this?
>
> Rick
>
> On Sat, Mar 28, 2015 at 6:20 PM, Domenic Denicola <d@domenic.me> wrote:
>
>>  Overall I really like this. It definitely affirms that a sourceDevice
>> property would have room to grow into something genuinely useful, as people
>> come up with more use cases that might desire the various properties you’ve
>> sketched out. Great stuff!
>>
>>
>>
>> *From:* rbyers@google.com [mailto:rbyers@google.com] *On Behalf Of *Rick
>> Byers
>> *Sent:* Tuesday, March 24, 2015 12:08
>> *To:* www-dom@w3.org; Gary Kacmarcik (Кошмарчик); Domenic Denicola;
>> Mustaq Ahmed; public-touchevents@w3.org; lanwei@chromium.org
>> *Subject:* Re: [DOM3Events] InputDevice API sketch
>>
>>
>>
>> Ping.  Any thoughts on whether DOM events should start going down this
>> path of exposing 'sourceDevice' information?   Domenic, you asked for the
>> design sketch - any thoughts?
>>
>>
>>
>> We've been dancing around this problem of separating logical events from
>> lower level physical input device information for years and I think the web
>> has suffered as a result (with all the guess work developers need to do on
>> the web compared to native platforms).  Any suggestions on how to enable
>> progress here?
>>
>>
>>
>> Rick
>>
>>
>>
>> On Mon, Mar 9, 2015 at 11:17 AM, Rick Byers <rbyers@chromium.org> wrote:
>>
>>  +public-touchevents (sorry for the spam).
>>
>>
>>
>> On Mon, Mar 9, 2015 at 11:04 AM, Rick Byers <rbyers@chromium.org> wrote:
>>
>>  In our latest discussion of how best to identify mouse events derived
>> from touch events, I proposed a 'sourceDevice' property
>> <https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0052.html>.  Domenic
>> asked <https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0052.html>
>> for a rough sketch of what such an InputDevice API might grow to become.
>> Here
>> <https://docs.google.com/a/chromium.org/document/d/1WLadG2dn4vlCewOmUtUEoRsThiptC7Ox28CRmYUn8Uw/edit>
>> is my first attempt at such a sketch, including some detailed references to
>> similar APIs in other platforms.  Any thoughts?
>>
>>
>>
>> Note that at the moment I'm primarily interested in standardizing and
>> implementing the 'firesTouchEvents' bit.  However if it makes more sense
>> for coherency, I'd also support adding (and implementing in chromium) a few
>> of the other non-controversial pieces.
>>
>>
>>
>> Rick
>>
>>
>>
>>
>>
>>
>>
>
>