#770: Delta review (to CR) of WebXR Gamepads Module

Visit on Github.

Opened Sep 7, 2022

Wotcher TAG!

I'm requesting a TAG review of WebXR Gamepads Module.

This specification module describes support for accessing button, trigger, thumbstick, and touchpad data associated with virtual reality (VR) and augmented reality (AR) devices on the Web.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: delta review request for CR transition (no solid date)
  • The group where the work on this specification is currently being done: Immersive Web WG
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
  • Major unresolved issues with or opposition to this specification: N/A
  • This work is being funded by: N/A

You should also know that...

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

Discussions

Discussed Oct 1, 2022 (See Github)

Dan: less certain on this one as list of changes seems similarly small but Tess might have more opinions.

Rossen: in their explainer - they allow you to map gamepad behaviour to other sources such as occulus touch, daydream, etc... which is good. the thing that's interesting: the gamepad instance must not be included... ID must be entry string, etc...

Peter: one of their changes - they're allowing it even if there is no xr session.. if they're gonna do it then it seems odd to exclude it from the regular list of gamepads... So seems a little thought needs to go into it.

Dan: so they are positioning this as an alternative to the gamepad API?

Peter: sort of, yea....

Dan leaves 2 comments - marked pending feedback

Comment by @torgo Oct 10, 2022 (See Github)

One question that came up in our discussions today on this – Are there any updates that need to be made to the explainer based on the listed changes to the spec?

Comment by @torgo Oct 10, 2022 (See Github)

Also … it seems from https://github.com/immersive-web/webxr-gamepads-module/pull/49 that you're talking about exposing the gamepad outside of the XR environment? If so, then doesn't this "compete" with the plain gamepad API?

Comment by @cabanier Oct 10, 2022 (See Github)

I think that should be a note. The intent is to clarify that a gamepad can be exposed through the regular gamepad api and WebXR at the same time.

Discussed Nov 1, 2022 (See Github)

Dan: Rick has said that the intent is to clarify a gampad can be exposed through regular api and webxr at the same time... I don't think they've really addressed the issue.

Yves: was okay minus this issue with negative index [??] - they need to fix that

Dan: about this particular thing, the webxr gamepad, their list of changes is small. I feel we need to set this to proposed closed. I don't think we can close without tess. Can we close at plenary?

Yves: I don't think there is something more as a delta

Discussed Nov 1, 2022 (See Github)

Dan: there was a response... should we wait for Tess?

Discussed Dec 1, 2022 (See Github)

we agreed to close

Comment by @torgo Dec 19, 2022 (See Github)

Hi @cabanier thanks for sending us this review. We're happy to see this go forward. Thanks for flying TAG and see you in the New Year.