Re: [w3c/gamepad] Added GamepadPose and GamepadCapabilities (#25)

> +        <dd>
> +          Angular acceleration of the gamepad in meters per second. MUST be null
> +          if the sensor is incapable of providing angular acceleration. When not
> +          null MUST be a three-element array.
> +        </dd>
> +      </dl>
> +    </section>
> +
> +    <section>
> +      <h2><dfn>GamepadCapabilities</dfn> Interface</h2>
> +      <p>
> +        This interface defines the gamepad's hardware capabilities.
> +      </p>
> +
> +      <dl title='interface GamepadCapabilities' class='idl'>
> +        <dt>readonly attribute boolean hasPosition</dt>

I felt this was necessary for the same reason we have the capabilities structure in WebVR: a null pose.position may not actually mean the device is incapable of reporting it, only that it can't report it right now. I do feel it's important to be able to differentiate those two cases.

That said, it probably is a mistake to have it in the same PR as the pose. Two proposals:
  1. I move this to it's own PR so that this one can focus on pose exclusively. (Pose is still usable without the capabilities, just not as developer friendly)
  2. We merge the capability booleans into the pose interface. This would mark another difference from the same interface in WebVR, but I wouldn't object to it.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/25/files/352f178964cf1c7c81fb2323d41d50d07c73e366#r71563736