A chromium flag --enablegamepads to enable gamepads without pressing a button first
Reported by
alexandros.vourtsis@gmail.com,
Nov 19 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Use the Gamepad API on a NW.js app 2. Notice how you have to press a button first before you can use gamepads What is the expected behavior? There should be a chromium flag --enablegamepads that would: 1. enumerate & enable connected gamepads & the API on application start without the need to press a button on a gamepad. That would allow us to use that flag in the NW.js app's package.json so the gamepads are enabled from the get go. 2. allow gamepads to access certain normally blocked off features such as the fullscreen API What went wrong? I am developing desktop applications using NW.js ( https://nwjs.io/ ) Using the Gamepad API for a game requires that the player presses a button before he is able to use any of the gamepad buttons. This is confusing e.g. when a message "PRESS START BUTTON" appears on the screen and the player has to press a face button for the gamepad to active first, *then* the start button. It also makes debugging a bit slower & annoying as a result. Did this work before? No Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Nov 21 2017
Tested the issue on windows 7 using chrome M62 #62.0.3202.94 and followed below steps : 1. Launched chrome and navigated to "https://nwjs.io/" and downloaded the stable package and checked for the exe file and launched it . 2. Parallely gamepad Sony has been connected through USb cable to the machine and couldn't proceed further. @alexandros.vourtsis-- Could you providedetailed steps and possible help us with the screencast of the steps to reproduce the issue , so that it would help help us in traiging the issue better. Thanks!
,
Nov 30 2017
Transitioning to Fullscreen is tracked in https://bugs.chromium.org/p/chromium/issues/detail?id=381596 and will have a different solution. For the use case of displaying "Press START" and waiting for user input, instead install an event listener to ongamepadconnected and react when any button is pressed. https://developer.mozilla.org/en-US/docs/Web/API/Window/ongamepadconnected If the desired use cases are still not satisfied, please clarify what is needed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sc00335...@techmahindra.com
, Nov 20 2017Labels: Triaged-ET TE-NeedsTriageFromHYD Needs-Triage-M62 TE-Hardware-Dependency