Bluetooth controller input changed after a browser upgrade

Your Bluetooth controller connected, but a browser game no longer sees it after an update. Or the sticks work while buttons or vibration do not. First check whether the browser receives the controller's inputs, then separate a browser problem from a connection or hardware issue.

TooLab's Test Everything runs checks step by step and gives you a report. For a closer look at the controller, use the Gamepad Test to check buttons, sticks, triggers, and vibration.

Check the controller in your browser

1. Open Test Everything and follow the test steps until you reach the gamepad check. Keep the controller close to the computer and make sure it is switched on.
2. Press a controller button, then move each stick and squeeze each trigger. Watch for the test to register each input. If you want to repeat or inspect controller inputs on their own, open the Gamepad Test.
3. If no controller appears at first, click or tap the test page, then press a controller button again. Some browsers wait for input before exposing a connected controller to a page.
4. Record what works and what does not. If you have results from before the browser upgrade, compare the same buttons and movements. Otherwise, try the same controller in another browser on the same device.

Keep the controller, computer, and connection method the same when comparing browsers. If you change several things at once, it becomes harder to find what changed.

What the result means

The test detects the controller and all controls respond

The browser can receive the controller's input. If a particular game still ignores it, check that game's controller settings and button mapping. The browser test confirms input reaches the page, but it cannot confirm how a separate game handles that input.

The controller appears, but one button, stick, or trigger does not respond

The browser is receiving at least some input, so the problem may be a specific control, a controller profile, or a mapping. Repeat the check in the focused Gamepad Test. If the same control fails there and in another browser, suspect the controller or its configuration rather than the browser update.

The controller is paired, but the test does not detect it

Bluetooth pairing only means the computer has connected to the controller. It does not guarantee the browser exposes the device to a page. Check that the controller is connected as an input device, then click the test page and press a button. If it still does not appear, compare with another browser.

Buttons and movement work, but vibration does not

Input and vibration are separate features. The controller may not support browser vibration, or the browser or operating system may not pass it through. A missing vibration response alone does not show that the controller's buttons or sticks are faulty.

How to fix it

1. Wake the controller and press a button. Some controllers sleep after sitting unused. Turn it on, click the test page, then press a button to prompt the browser to check for input.
2. Check the Bluetooth connection. On Windows 11, open Settings › Bluetooth & devices › Devices and confirm the controller is connected. On macOS, open System Settings › Bluetooth. On Android, check Settings › Connected devices. On iPhone or iPad, check Settings › Bluetooth.
3. Disconnect and reconnect the controller. Turn it off, wait a few seconds, then turn it on again. If it remains connected but sends no input, remove or forget it in the device's Bluetooth settings and pair it again using the controller maker's instructions.
4. Restart the browser. Close all browser windows and reopen the browser, then run the test again. If the controller works after restarting, a browser process may have kept an old connection state.
5. Compare in another browser. Run the same test with the same controller and device. If it works there but not in the upgraded browser, temporarily disable extensions or check that browser's updated settings. If it fails in both browsers, focus on Bluetooth, controller settings, or the controller itself.
6. Restart the device. A restart can clear a stuck Bluetooth connection or browser process. Pair the controller again and test before opening a game or another controller app.

On a phone or tablet, browser support for game controllers can vary. If Bluetooth shows the controller as connected but a browser test does not see it, try a supported computer browser before concluding the controller is broken.

When it may be the controller

If the same button or stick fails in the Gamepad Test and another browser, disconnect the controller and check it in a game or system feature that normally accepts it. If that control still fails, charge or replace the batteries and check the controller's instructions for a reset or profile switch. Persistent failures across devices point to a controller fault. Check its warranty or arrange a repair before replacing it.

Why a browser upgrade can change detection

A browser can change how it reads gamepad input or when it makes a controller visible to a web page. That does not necessarily mean the update damaged Bluetooth or the controller. A page may need a fresh click and a new button press before it receives input, and a browser test cannot check how every game handles controller support.

For a fair comparison, use the same controller, device, browser profile, and controls each time, and note any differences before changing settings.