New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 613429 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
bajones@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

ADT/Nexus Player Gamepad regression on Windows

Reported by aicomman...@gmail.com, May 20 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. Connect the Nexus Player or ADT1 gamepad to your Windows PC
2. Go to html5gamepad.com

What is the expected behavior?
Buttons should work correctly

What went wrong?
No buttons work, except for buttons that are really raw axes (dpad and triggers).

Did this work before? Yes Prior to a8d9d22865f445b8f6f2b9814fb919b8008fbc5c

Chrome version: 52.0.2741.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

My change regressed this gamepad on Windows. When I dump the HID descriptor on OSX, I see that the buttons have a usage page of 0x09 as expected. However, when I added additional debugging on Chrome on Windows, it's reporting a usage page of 0x0C. That doesn't really make sense to me at all, since HID is supposed to be the same across operating systems.

IMHO, it's not worth reverting the commit as the bug it was fixing had a more widespread effect. We could try an alternate fix where we only skip buttons with usage page 0xFF but that seems more brittle. We should discuss where we go from here.

Offending commit: https://chromium.googlesource.com/chromium/src/+/a8d9d22865f445b8f6f2b9814fb919b8008fbc5c

Comment 1 by brajkumar@chromium.org, May 20 2016

Cc: bajones@chromium.org brajkumar@chromium.org
Components: IO>Gamepad
Tested this issue on Windows 7 using chrome latest canary M52-52.0.2743.0 by using Logitech Gamepad F310. 

1, Navigated to the site html5gamepad.com
2. Clicked the buttons in the game pad
3. Observed the actions are displayed in the HTML5 Gamepad tested.

As per the above CL adding the reviewer of the file for more update on this issue.

@bajones - Could you please look in to this issue?
Gamepad.mp4
489 KB Download

Comment 2 by aicomman...@gmail.com, May 20 2016 

FWIW, Firefox also has the same behavior with the Nexus Player gamepad (no buttons work).

Comment 3 by brajkumar@chromium.org, May 24 2016

Labels: Needs-Feedback
bajones@ - Could you please look in to this issue?

Comment 4 by ajha@chromium.org, May 26 2016

Labels: TE-Hardware-Dependency

Comment 5 by scheib@chromium.org, Apr 20 2017

Labels: Pri-3
Issues not modified in last 50 days aren't on track to ship in next release.

Comment 6 by reillyg@chromium.org, Apr 27 2017

Components: -IO>Gamepad Blink>GamepadAPI

Comment 7 by mattreynolds@chromium.org, Sep 13 2017

Status: Available (was: Unconfirmed)
Tested with an ADT1 (I think... hwids are 18d1:2c40) and confirmed that button presses are not received except for D-pad and triggers in Chrome on Windows (60.0.3112.101).

I also tested on other platforms. On all platforms, (Linux desktop, Chrome OS, Android, OSX) the Mode button was not fully functional. On 5-10% of presses, a button press is reported for a single frame when the button is released. The rest of the time, Mode presses are ignored. This might just be a defect of the device I was testing.

On Android, Back and Home are mapped to OS keys. On Linux, they are mapped to the Chrome Back and Home navigation buttons. On Chrome OS and OS X they are unmapped.
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 14

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by mattreynolds@chromium.org, Sep 19

Status: Available (was: Untriaged)
►

Sign in to add a comment