squint
Chrome does things differently here. Instead of constantly storing the gamepad's latest state in a variable it only stores a snapshot, so to do the same thing in Chrome you have to keep polling it and then only use the Gamepad object in code when it is available.
squint again
This property MUST be true if the button is currently pressed, and false if it is not pressed.
ok so chrome is just violating the spec then?? so everyone has to work around it by doing the same thing the browser should be doing but in javascript where it's slower. classic
