Device Bench

Device test · Input

Mouse Button Test

Press each button inside the test area, then scroll up and down.

Detected0/5 Button— Clicks0 Scroll0 Interval— Double-clicks0

Keep the pointer over the diagram while testing. Browser actions are suppressed here where possible; side buttons may still navigate.

Verdict

NOT RUN

—

Click each button a few times to check it. An unintended double-click is two presses of the same button under 80 ms apart.

Published thresholds: 0 unintended double-clicks on a button is PASS. 1–2 is CHECK SETTINGS — rapid intentional clicking can trip this too. 3 or more on the same button is LIKELY FAULT, consistent with a worn switch. Full reasoning in the methodology.

If it's flagged

    How this test works

    This page is a mouse button test, a scroll wheel test and a double-click test in one pass. It listens for pointerdown events inside the diagram, or mousedown events in browsers without Pointer Events. Clicks totals the presses it counts, and Button names the latest one, using the standard button indices: 0 for left, 1 for the wheel button, 2 for right, and 3 and 4 for back and forward. Touch and pen input is skipped, because a tap reports itself as a left-button press; the mouse-event fallback carries no pointer type, so it cannot make that distinction.

    Interval is the time between the last two presses of the same button, measured when the page handles each event, so a button's first press shows none. A gap under 80 ms adds to Misfires, and a gap from 80 ms up to just under 150 ms is labeled fast without being flagged. The readout rounds to whole milliseconds while the label uses the exact gap. A jitter click can land under 80 ms too, so one flag during fast clicking may be you; misfires that keep adding up during ordinary single clicks point to the switch.

    Scroll counts wheel events that move vertically, and the arrows light in the reported direction; horizontal-only scrolling is not counted. Inside the test area the page blocks page scrolling, the context menu, middle-click actions and side-button navigation, which is what makes a right-click test possible in a browser. Some browser-level actions can still take priority. Outside the area, your browser behaves normally.

    Frequently asked questions

    Why does my browser go back when I press a side button?
    Some browsers act on the back and forward buttons (X1 and X2) before this page can cancel them. The tester blocks that navigation inside the test area where the browser allows it. If the page still goes back, the button works: the browser received the press and acted on it.
    What does the Misfires counter mean?
    It counts presses of the same button that land less than 80 ms after the previous one. During ordinary single clicks, a gap that short usually means a worn switch bouncing and sending a second click you did not make. Fast intentional clicking can trip it too, so look at the pattern: choose Reset test, make single clicks with a full release between each, and watch whether misfires keep adding up.
    My mouse has extra buttons that don't register here. Why?
    The diagram shows the five standard buttons: left, middle, right, back and forward. Extra buttons such as DPI switches, sniper buttons and thumb grids are usually handled by the mouse's own software, which maps them to keyboard shortcuts or macros before the browser sees a mouse button. If the browser does report another button, the readout shows it as Button followed by its number. For a button mapped to a keystroke, use the keyboard tester, though the browser may still act on its own shortcuts first.
    Why doesn't the scroll count match the notches I feel?
    The counter adds one per wheel event, and one notch does not always produce one event. Smooth scrolling can split a notch into several small events, a free-spinning wheel sends a long stream of them, and touchpads report continuous motion with no notches at all. Use the counter to confirm that the wheel responds in both directions.
    Can this test fix a double-clicking mouse?
    No. A bouncing switch is mechanical wear, and software cannot repair it. Some mouse utilities hide the problem by raising the click debounce time, at the cost of ignoring fast intentional double-clicks. The lasting fixes are a warranty claim or a switch replacement, which is a routine repair on most mice.

    Related tools