I tend to agree for Audio; this is why I did write the Launch button. For the Gamepad API, if the browser does not want to expose model information, it should e

I tend to agree for Audio; this is why I did write the Launch button. For the Gamepad API, if the browser does not want to expose model information, it should either: - expose the buttons as sent by the OS, and let the OS to the mappings - or build its own internal game controller db for mappings. Right now it's doing neither, and that's an issue.