W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2015

RE: [DOM3Events] InputDevice API sketch

From: Domenic Denicola <d@domenic.me>
Date: Sat, 28 Mar 2015 22:20:22 +0000
To: Rick Byers <rbyers@chromium.org>, "www-dom@w3.org" <www-dom@w3.org>, Gary Kacmarcik (Кошмарчик) <garykac@chromium.org>, Mustaq Ahmed <mustaq@chromium.org>, "public-touchevents@w3.org" <public-touchevents@w3.org>, "lanwei@chromium.org" <lanwei@chromium.org>
Message-ID: <CY1PR0501MB1369A90C05CC2DCCC7D6215ADFF70@CY1PR0501MB1369.namprd05.prod.outlook.com>
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?


On Mon, Mar 9, 2015 at 11:17 AM, Rick Byers <rbyers@chromium.org<mailto:rbyers@chromium.org>> wrote:
+public-touchevents (sorry for the spam).

On Mon, Mar 9, 2015 at 11:04 AM, Rick Byers <rbyers@chromium.org<mailto: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.


Received on Saturday, 28 March 2015 22:20:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:23 UTC