- From: Rick Byers <rbyers@chromium.org>
- Date: Mon, 9 Mar 2015 11:04:42 -0400
- To: "www-dom@w3.org" <www-dom@w3.org>, Gary Kacmarcik (Кошмарчик) <garykac@chromium.org>, Domenic Denicola <d@domenic.me>, Mustaq Ahmed <mustaq@chromium.org>
- Message-ID: <CAFUtAY-iud-+MHZemjZp3-7miiNkxbvzr=bHyv_8qf57MSKGEw@mail.gmail.com>
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 Monday, 9 March 2015 15:05:29 UTC