Mouse Button Test
Check which left, right, middle, back, and forward button events reach this browser. The result describes observed browser events, not internal switch condition.
Press mouse buttons in this area
Try Left, Right, Middle, Back, and Forward. Context menus and side-button navigation are suppressed only inside this box.
Left
Not observed yet
Events: 0
Latest: —
Middle
Not observed yet
Events: 0
Latest: —
Right
Not observed yet
Events: 0
Latest: —
Back
Not observed yet
Events: 0
Latest: —
Browser/OS may reserve this button
Forward
Not observed yet
Events: 0
Latest: —
Browser/OS may reserve this button
How to use
- Place the pointer inside the test area.
- Press each mouse button you want to check at least once.
- Review the count and latest observed time, then use Reset before repeating the same sequence.
Read the results
- Observed means this page received that button event during the current session.
- Not observed yet means the page has not received it; it does not by itself mean the button is broken.
- Back and Forward may remain unavailable because the browser, operating system, or mouse software reserves them.
Limits and retesting
- Only events exposed to the browser can be shown; firmware and electrical switch behavior are not inspected.
- Repeat in another browser or computer after changing one variable at a time.
- Outside the marked area, normal context-menu and browser navigation behavior remains available.
Common situations this test can investigate
Use the page to collect a repeatable browser observation before changing cables, settings, software, or devices.
A button does not respond in one app
Check whether the same physical press reaches the browser. If it appears here but not in the app, compare that app's shortcuts, permissions, and button mapping.
A side button navigates unexpectedly
Observe whether Back or Forward reaches the page, then compare behavior outside the test region. Browser navigation and mouse remapping software may take priority.
A press seems to register more than once
Reset the counters and make five separated presses. Compare the observed count with the deliberate press count before changing one part of the setup.
A repeatable troubleshooting sequence
- 1Reset the session and make five slow, deliberate presses with only one button. Avoid dragging the mouse while counting.
- 2Compare the button's event count with your physical press count and note the latest timestamp after the final press.
- 3Repeat once outside private browsing and with extensions or mouse remapping tools reviewed, because software may reserve or transform inputs.
- 4Change one variable—browser, USB port, wireless receiver position, cable, or computer—and repeat the same five-press sequence.
- 5Use the manufacturer's configuration or support tool if you need firmware, switch, warranty, or device-specific conclusions.
Browser event reference
- Left · button 0
- Usually the primary selection button exposed by browsers.
- Middle · button 1
- Usually the scroll-wheel press; scrolling the wheel is a separate wheel event.
- Right · button 2
- Usually the secondary button. Its context menu is suppressed only inside the test area.
- Back · button 3
- Common side-button code, often reserved for browser history or remapped by mouse software.
- Forward · button 4
- Common forward-navigation code with the same browser and software reservation limits.
Frequently asked questions
Why does the right-click menu not open in the test area?
The page suppresses the context menu only inside the marked test area so it can observe the right-button event. Right-click outside the area to use the browser menu normally.
Why are Back or Forward not observed?
A browser, operating system, extension, or mouse utility may reserve a side button for navigation before the page can use it. Compare another browser and review the mouse utility's button assignment.
Does two observed events from one press prove a bad switch?
No. Repeated events are useful evidence to reproduce, but browser scheduling, software remapping, remote-desktop tools, and the device can all affect delivery. Reset and repeat slowly on another setup.
Can a phone or touchscreen complete this test?
Touch interaction normally produces pointer or touch behavior rather than all five mouse-button codes. Use a connected mouse and a desktop-class browser for the intended test.