I have a repro with my Logitech Dual Action controller. The X button is stuck down in Chrome on Windows but not on OS X.

I have a CL that will address the stuck button that I'll upload soon. The d-pad issue is simply a missing gamepad mapping issue.

 Issue 393164  has been merged into this issue.

Thanks for the heads up. Much appreciated.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a8d9d22865f445b8f6f2b9814fb919b8008fbc5c

commit a8d9d22865f445b8f6f2b9814fb919b8008fbc5c
Author: aicommander <aicommander@gmail.com>
Date: Wed May 04 20:08:27 2016

Fix button 1 being stuck down on certain Logitech gamepads on Windows

There are HID elements in these gamepads classified as buttons which
don't use the usage page value for buttons. These elements don't actually
correspond to real buttons on the controller, and are stuck in the pressed
position. On OSX, we skip these "fake" buttons, but we didn't on Windows.
As a result, a HID element would overlap with button 1 and make it appear
to be constantly pressed.

R=bajones@chromium.org

BUG= 600230 

Review-Url: https://codereview.chromium.org/1950883002
Cr-Commit-Position: refs/heads/master@{#391616}

[modify] https://crrev.com/a8d9d22865f445b8f6f2b9814fb919b8008fbc5c/content/browser/gamepad/raw_input_data_fetcher_win.cc

aicommander@: Shall we close this if there is no further work to be done on this.

Well, there's still the missing mapping for certain d-pads. I'm still unsure why Firefox can somehow have that displayed correctly and chrome can't.

Firefox will automatically convert axis 9 (HID usage 0x39, specified to be a D-Pad) into buttons. That's the reason you see buttons instead of an axis. Chrome doesn't do that, so you see the raw axis that the device exposes. It wouldn't be difficult to duplicate Firefox's behavior, but I want to have a discussion/resolution on the regression in 613429 before making further HID changes.

@#7, Thanks for the reply. Since it would seem that the other part of this bug has been fixed, I'd say it's probably fine to close this report.

Also, if you need a more visual representation of Gamepad API data, feel free to use my own tool http://gamepadviewer.com/. There's also a live raw output similar to html5gamepad.com's in the remapping modal, just make sure to select the appropriate player.

As ^