FxR controller and display names should match the native browser's names.

[bluemarvin]

Hardware

All

Current Behavior

We use the same names on all platforms and do not match any existing platforms.

Possible Solution

We should examine what names are used in each native browser and emulate them. A lot of code is already sniffing for specific platform names and it would be easier to just emulate than try and get existing websites to update their code to look for FxR specific strings.

Context

The FxR controller doesn't work on sketchfab.com because they are looking for specific controller names in their code.

[cvan]

Good catch. Removing Gamepad#id (the "display name") has come up quite a bit in spec discussions:

• id field in gamepad might have a persistent identifier? w3c/gamepad#73
• About the id w3c/gamepad#65
• "id" property is unclear how its established w3c/gamepad#9
• Gamepad objects should have a dictionary of attributes about the controller and data source w3c/gamepad#12

I understand that the main reason for the Gamepad#id sniffing is to ensure the buttons and axes are mapped correctly (or re-mapped for particular browser/OS/gamepad configurations, which I myself had to do quite a bit in making HTML5 games).

If there's not already enough information with the current properties, a dictionary of capabilities (per w3c/gamepad#12) could be added so developers don't need to sniff for the name.

[MortimerGoro]

We use the same names on all platforms and do not match any existing platforms.

Actually we have already set different names for each display, so it should report different names on each. But yep, it's good to check we are using names that apps are checking correctly.

For the controllers we set the ones used in AFrame (e.g "Gear VR Remote Controller")

[avrignaud]

@larsbergstrom and I will figure out webcompat loop.

[cvan]

Whichever we choose, we should make sure they are supported by those defined in this popular library used with three.js: https://github.com/stewdio/THREE.VRController/blob/master/VRController.js. (And obviously make PRs when appropriate.) Oculus Go Controller has been recently added, FYI.

[philip-lamb]

See also #812 and #770.

[cvan]

I've commented on w3c/gamepad#73 (comment). Will update as I do some research on the actual sites possibly impacted by Gamepad#id sniffing.

[cvan]

Is there more to be done here? Oculus Go + VIVE Focus Gamepad#id strings were changed in issue #812 / PR #981.

[philip-lamb]

Closing as resolved.