- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Fri, 21 Jun 2013 09:02:45 -0400
- To: Alan Kligman <ack@mozilla.com>, scottmg@google.com, Ted Mielczarek <tmielczarek@mozilla.com>
- CC: public-webapps@w3.org
On 6/19/13 2:37 PM, ext Alan Kligman wrote: > Hey all, > > This is mostly a follow-on to Ted's email from last month (http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0478.html). There are still some issues that would be great to clarify in the spec: > > 1. Analog+digital buttons (as with the PS3 controller), need to be reported such that upstream code can determine that the axis and button refer to the same physical input. > * There are a few ways to do this, but we should decide on one and define it in the spec > * It would be nice to describe it in this version of the spec, since it could break backward compatibility if changed later Is this covered by bug 21388 <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21388>? > 2. Clarify liveness of gamepad object > * Ted and Scott started a discussion, but I don't think the spec has been updated yet: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21434 > * This could break backward compatibility if it's changed later, so it would be nice to clarify this in the spec > > 3. Expose axis, button metadata (if available) > * Report things like button names, if we have them > * Require (instead of suggest) that the id property contains USB vendor/product numbers, so that we can reliably map controllers in application code <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21386>? > I think 1 and 2 are important to resolve soon so that we avoid breaking application code using the gamepad API. > > Thoughts? > A > >
Received on Friday, 21 June 2013 13:03:17 UTC