Thanks for the additional details. I was able to reproduce the issue. It seems that it's caused by the browser sending joypad axis input, even when there's no gamepad connected. We will upload a fix as soon as possible.