I'd like to note that the current semantic (in google chrome) of "press button to connect device" is not very user friendly. Not all buttons register as buttons (some register as axes) and won't do anything. Some devices are also devoid of buttons (like the oculus rift) to press.
On Thu, May 2, 2013 at 4:45 PM, Ted Mielczarek <t...@mozilla.com> wrote: > Hello there, > > The Gamepad spec hasn't seen a lot of activity lately, and it's > primarily my fault. I got tied up in other work and didn't have time to > work on my implementation in Firefox or the spec. I dug out of that and > managed to land an initial implementation which is currently available > in Firefox nightly builds, and I've been making small changes to the > spec to clean up some issues. While fixing up my implementation to match > the spec and testing vs. Scott's implementation in Chrome I've found a > few spec issues that we'll have to work through. I'll detail these in > separate emails shortly. > > I'd like to get both the spec and my implementation into a shippable > state in the very near future, so I don't want to add any significant > new features. I'd just like to clarify and tighten up the language so we > can be sure to ship interoperable implementations and also not make > future spec work difficult. > > Regards, > -Ted > > > >
