Logitech Cordless Rumblepad 2's facebutton mappings are off as are the axes, the d-pad is unmapped.

UNCONFIRMED
Unassigned

Status

()

P5
normal
UNCONFIRMED
5 years ago
5 months ago

People

(Reporter: samu.agarwal, Unassigned)

Tracking

(Depends on: 1 bug)

32 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

Step 1: Go to http://www.html5rocks.com/en/tutorials/doodles/gamepad/gamepad-tester/tester.html
Step 2: Plug in gamepad
Step 3: Press random buttons till it connects.



Actual results:

The mappings of the face buttons were wrong(X is button 1 instead of A being button 1), the axes were offset by one(axe[1] should be axe[0])


Expected results:

The buttons on the gamepad should have corresponded to the buttons show on the image.
(Reporter)

Comment 1

5 years ago
I think quite a few logitech gamepads would have this issue because the first logitech gamepads had button 1 be in the 9 o'clock position instead of the 6 o'clock position like xbox gamepads(which W3C calls the STANDARD gamepad layout). Then they just put a punch a letters on instead of actually changing the mappings when they realised that the xbox ABXY layout was considered the informal standard in the gaming community.

TL;DR I suspect that this issue affects 8 gamepads(based on the the number of gamepads for PC on the logitech support website)
(Reporter)

Comment 2

5 years ago
Also, the superbutton(Big X in centre on xbox gamepad, PS logo on dualshock 3, logitech logo on Rumblepad 2) doesn't get mapped at all.
(Reporter)

Comment 3

5 years ago
The D-PAD doesn't get mapped either.
Summary: Logitech Cordless Rumblepad 2's facebutton mappings are off as are the axes → Logitech Cordless Rumblepad 2's facebutton mappings are off as are the axes, the d-pad is unmapped.
(Reporter)

Updated

5 years ago
Severity: normal → minor
(Reporter)

Updated

5 years ago
Severity: minor → normal
(Reporter)

Comment 4

5 years ago
I decided to keep it at normal because it affects atleast 8 gamepads, and is therefore inconviences more users.
Component: Untriaged → DOM
Product: Firefox → Core
This is really hard to get right in the general case. Gamepads are all over the place with what they report in their HID descriptors. I think exposing enough data to content to allow it to make informed decisions is the only way to make this work.

Updated

5 months ago
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.