[gamepad-controls] gamepad handling in FF vs Chrome?

[kylebakerio]

trafficstars

This is not the fault of this library in any way, but I'm seeing my very vanilla, common, basic gamepad work perfectly in chrome, and be waaay off in FF. Looking at a gamepad tester, and looking in the console at the returned values, I see that this is probably because FF maps this controller quite differently (and admittedly worse) than Chrome does.

Is there any way to handle this that you're aware of? All the buttons and axes are there in both, but in FF the variable-sensitivity triggers are reported as axes, for example, as are the dpad buttons. (Chrome says 4 axes and 17 buttons, FF says 8 axes and 11 buttons).

I've already got a work-in-progress button-mapping component I've designed that works fine for chrome, I'm imagining I probably just need to expand it to detect axis values as well now, basically. I'm just going to have to look into how to manually change the stuff that movement controls does in the background, I think.

Any interest on a pull request for this type of thing, and if so, any thoughts on implementation?

[vincentfretin]

Still an issue?