Design Review #770

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

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.

Explainer¹ (minimally containing user needs and example code): https://github.com/immersive-web/webxr-gamepads-module/blob/master/gamepads-module-explainer.md
Specification URL: https://www.w3.org/TR/webxr-gamepads-module-1/
Tests: https://github.com/web-platform-tests/wpt/tree/master/webxr/gamepads-module
User research: N/A
Security and Privacy self-review²: https://github.com/immersive-web/webxr-gamepads-module/issues/56
GitHub repo (if you prefer feedback filed there): https://github.com/immersive-web/webxr-gamepads-module/
Primary contacts (and their relationship to the specification):
- Manish Goregaokar, @Manishearth, Google, Editor
- Brandon Jones, @toji, Google, Editor
- Rik Cabanier, @cabanier, Meta
- Ada Rose Cannon, @AdaRoseCannon, Apple, Chair
- Chris Wilson, @cwilso, Google, Chair
- Ayşegül Yönet, @Yonet , Microsoft
Organization(s)/project(s) driving the specification: Immersive Web WG
Key pieces of existing multi-stakeholder review or discussion of this specification: N/A
External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
- Chrome status: https://chromestatus.com/feature/5659025263820800

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...

Last TAG review was #430 (2019/Oct), right after FPWD
- one unresolved issue from last review, https://github.com/immersive-web/webxr-gamepads-module/issues/27, handed to Gamepad API https://github.com/w3c/gamepad/pull/158
Please see changes from FPWD

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

2022-10-10

Minutes

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

2022-11-14

Minutes

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

2022-11-28

Minutes

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

2022-12-19

Minutes

we agreed to close