2 ms·
Interesting that the pitfalls for developers are both wins for the end user. I don't want my browser to know what kind of peripherals I'm using or be able to pl
by AlecSchueler 3y ago
Interesting that the pitfalls for developers are both wins for the end user. I don't want my browser to know what kind of peripherals I'm using or be able to play audio I didn't explicitly ask for.
How would something like the sdl gamecontroller db work in this context?
- Aissen 3y agoI 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.