- From: <bugzilla@jessica.w3.org>
- Date: Sun, 30 Mar 2014 22:39:34 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25202 Brandon Jones <bajones@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bajones@google.com --- Comment #2 from Brandon Jones <bajones@google.com> --- Some things to consider: 1) You'd have to be careful about over-specifying the format to depend on signals that may not be present on all devices. For example: I don't think that Android would give you a vendor ID and product ID. XInput devices also don't provide many controller details unless you look at other APIs. 2) Not only could a controller be exposed differently between OSes, but the various browsers on the same OS may expose controller inputs differently. Assuming that ID strings were rigorously enforced across browsers in order to get a complete idea of how a controller is exposed you would then need to look at the id, the OS, and the browser as exposed by the User Agent string. :P The only time that the inputs will reasonably be the same across the board is if they have the mapping "standard", which _is_ well specced. I think the only reasonable route for developers to take when presented with a controller that doesn't conform to the "standard" mapping is to have the user run through a quick configuration dialog and then save the mapping the users provides. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 30 March 2014 22:39:35 UTC