Gamepad API not discovering connected gamepads in Chrome App

153 views

Skip to first unread message

Bryce Thorup

unread,

Mar 21, 2017, 1:42:09 PM3/21/17

to Chromium OS dev

I submitted a bug report at crbug.com a couple of weeks ago. It can be found here: https://bugs.chromium.org/p/chromium/issues/detail?id=699199

Basically, if you call navigator.getGamepads() in a Chrome App it reports no devices being connected. If you call the same function through a hosted page in the browser itself it works fine (once a button on the gamepad has been pressed). I attached an example setup in the bug report. It can be loaded as a chrome app, and then you can load index.html using a local server to test as a web app to see the difference (green = detected, red = not detected). I've also tracked down what I feel fairly certain to be the exact change in the code that broke the API. See the bug report for more details.

I understand fixes can take weeks or months to happen, but I'm posting here because it has been over a week and I've not got any response from the bug report, and wanted to get some closure on when/if this bug will be fixed, or if I should start looking for a different solution.

Mike Frysinger

unread,

Mar 21, 2017, 3:18:41 PM3/21/17

to Bryce Thorup, Chromium OS dev

not to punt, but seems like a problem with the browser rather than the OS. which means this group (the OS guys) would leave it to the browser/blink group to deal with.

there is chromium-dev@ and blink-dev@.

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

Bryce Thorup

unread,

Mar 21, 2017, 3:27:03 PM3/21/17

to Mike Frysinger, Chromium OS dev

Right on, I knew that too. I do most everything in Chrome OS so it is on my mind a lot. I'll shift it over to chromium-dev and see what response I can get. Thanks!