I've created a more formal proposal for an initial simple InputDevice API (though probably still sloppy by W3C spec standards). Please provide any additional feedback you have on it, ideally as GitHub issues (or feel free to submit pull requests, eg. for editorial improvements).
So what's the best path forward to starting to spec something here? Is the UI Events spec the best place to put this?
On Sat, Mar 28, 2015 at 6:20 PM, Domenic Denicola <[hidden email]> 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!
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?
In our latest discussion of how best to identify mouse events derived from touch events,
I proposed a 'sourceDevice' property. Domenic asked for a rough sketch of what such an InputDevice API might grow to become. Here
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