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'm comfortable with `Gamepad#pose`, but this one not so much. can you explain other instances that are not specific to VR when we need capabilities info. that cannot be discerned from the presence of buttons and axes and their values?

---
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#r71541557