Quick answer
What this guide helps you determine
Check connection, browser focus, button activation, mapping support and competing applications.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A browser may not list a gamepad until it is connected, recognized by the operating system, activated with a button and exposed by the current browser. Bluetooth pairing, cable type, platform mode and competing controller software can all affect that path.
Step-by-step method
- Verify the operating system sees the controller, then focus the browser page and press a standard face button. Try a known data-capable USB cable and direct port; some charging cables carry no data.
- For Bluetooth, confirm it is paired in the correct controller mode and not still connected to another host. Close remapping or virtual-controller applications for one comparison and reload the page.
- Compare another current browser and the system controller panel. If the OS never detects it, check battery, cable, firmware and platform compatibility. If only the browser fails, browser support or privacy activation is more likely.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Press a controller button after loading
- Reconnect USB or Bluetooth
- Try a current Chrome, Edge, Firefox or Safari release
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| OS sees it but page does not until a press | User activation was required. | Press a normal button after focusing the page. |
| Charging works but no input appears | The cable may lack data or the controller is in the wrong mode. | Use a documented data cable and mode. |
| A virtual controller appears instead | Remapping software is exposing an emulated device. | Close it or choose the intended entry. |
Common mistakes to avoid
- Do not install unsigned controller drivers from an unknown source.
- Do not delete all Bluetooth pairings unnecessarily.
- Do not conclude incompatibility from one browser alone.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “OS sees it but page does not until a press”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Why does Bluetooth show connected but no gamepad?
The device may be in a media/keyboard mode, connected to another host or unsupported by that browser mapping.
Can a charge-only cable cause this?
Yes. It can power the controller without carrying input data.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.