Ensure that the first button returned for VR controllers is the primary button.

NEW
Unassigned

Status

()

P2
normal
a year ago
a year ago

People

(Reporter: kip, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
We should swap the button mappings of VR controllers to ensure that primary button (usually trigger) is always first button. Currently trackpad click for OpenVR is first button, but should be the trigger.

With greater variety controllers being supported, especially with Microsoft Mixed Reality, WebVR developers will be increasingly dependent on the browser to identify this primary button consistently.
Indeed, Trigger should be the primary button for the various controllers. But, due to our implementation follows what Chromium did for consistent, it brings this kind of problem. If we decide to swap it, we will affect the current VR content... That's very tricky...
(Reporter)

Updated

a year ago
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.