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

Re: [DOM3Events] InputDevice API sketch

From: Кошмарчик <garykac@chromium.org>
Date: Tue, 24 Mar 2015 10:24:49 -0700
Message-ID: <CAGnkXoE87xZCb9pWKNaw1jqnPbcE3mhS=uJdSAj6hTGc1fhV_Q@mail.gmail.com>
To: Rick Byers <rbyers@chromium.org>
Cc: "www-dom@w3.org" <www-dom@w3.org>, Domenic Denicola <d@domenic.me>, Mustaq Ahmed <mustaq@chromium.org>, "public-touchevents@w3.org" <public-touchevents@w3.org>, lanwei@chromium.org
I'm glad to see the keyboard device info in the API sketch since that's
something we've tangled with in the Dom3Events (now UIEvents) spec. We know
roughly what keyboard device information we need to provide, but don't yet
have a satisfying place to house it. The InputDevice API looks good to me
from that standpoint.

On Tue, Mar 24, 2015 at 9:07 AM, Rick Byers <rbyers@chromium.org> wrote:

> 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
Received on Tuesday, 24 March 2015 17:25:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:06 UTC