Quick answer: Wait for the gamepadconnected event (or a first button press), then poll navigator.getGamepads every frame and read the live snapshot rather than caching it.

A controller the browser ignores is usually just waiting for a button press to reveal itself, or being read the wrong way. The Gamepad API has a specific flow. Here is how to use it.

How to fix it

1. Wait for connection or first press

For privacy, browsers hide a gamepad until the user presses a button on it. Listen for gamepadconnected, and prompt the player to press a button so it appears.

2. Poll getGamepads every frame

There is no event stream for button states; call navigator.getGamepads() each frame in your loop and read the current values. Treat it as a fresh snapshot, not a stored reference.

3. Read the live snapshot

The gamepad object from getGamepads is a snapshot; cached references can go stale. Re-fetch each frame and check connected before reading axes and buttons.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.