Quick answer
What this guide helps you determine
Verify digital button state and analog trigger values while accounting for different browser mappings.
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
Controller buttons may be digital, analog or mapped differently across browsers. Triggers often report a gradual value while face buttons usually report pressed state, but some devices expose both in vendor-specific ways.
Step-by-step method
- Activate the controller and select it, then press one control at a time. Watch both pressed state and numeric value. Release fully before moving to the next control so a sticky value is obvious.
- Squeeze each trigger slowly from rest to its physical stop and back. Press D-pad directions separately and in allowed diagonals. Then test the few simultaneous combinations used by the target game.
- Compare the game’s mapping screen because it may relabel or combine axes. If one control never reaches a useful range across systems, collect the observed values for manufacturer support rather than assigning a universal pass/fail threshold.
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 each control slowly
- Watch analog values reach their range
- Record the local button number only for your own mapping
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Button changes to pressed and returns | The complete control transition reached the browser. | Continue through the inventory. |
| Trigger value changes but uses an unexpected index | The mapping differs, not necessarily the hardware. | Identify it by motion and map it in the game. |
| A button remains active after release | Physical sticking, mapping or a lost disconnect event is possible. | Reconnect and compare the system controller panel. |
Common mistakes to avoid
- Do not compare raw index numbers across controller models as a quality metric.
- Do not force analog triggers.
- Do not share device-identifying labels in public reports.
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, “Button changes to pressed and returns”—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 is a trigger shown as both a button and a value?
Gamepad mappings can expose an analog trigger through a button slot with a gradual value and a pressed threshold.
Why does my D-pad use buttons instead of axes?
The standard mapping represents it as buttons in many browsers, while vendor mappings can differ.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.