▮ Device Bench

Device test · Input

Mouse Test

Press every button inside the test area, spin the wheel both ways, and watch the interval readout — two presses of the same button under 80 ms apart usually mean a worn switch, not your finger. Everything runs locally in your browser; nothing you click is sent anywhere.

Button— Clicks0 Scroll0 Interval— Misfires0

Test inside this area — the context menu, middle-click actions, and back/forward navigation are suppressed here only.

How this test works

The tester records three things inside the test area: which of the five standard mouse buttons the browser reports on each press, how many wheel events fire in each direction, and the time between consecutive presses of the same button. That last measurement is the point of the tool — a worn switch bounces, and the bounce shows up as an impossibly short gap between two clicks that were meant to be one.

Each press arrives as a pointer event carrying a button index — 0 for left, 1 for the wheel, 2 for right, 3 and 4 for the side buttons — and is timestamped with the browser's high-resolution clock. Inside the test area the page suppresses the context menu, middle-click actions, and back/forward navigation so every button can be pressed safely; outside it, your browser behaves normally. Touch and stylus input is ignored entirely — a tap reports itself as a left-button press, and a mouse test that counted taps would be measuring the wrong device. The wheel listener is registered non-passive so testing the wheel never scrolls the page. A same-button gap under 80 ms is counted as a likely misfire: switch bounce typically registers within a few tens of milliseconds, while even very fast deliberate double-clicking sits comfortably above that line. Gaps between 80 and 150 ms are labeled fast but not flagged.

The threshold is a heuristic, not a verdict. A deliberate jitter-click can land under 80 ms and produce a false flag, so the counter is meant to reveal a pattern — misfires that accumulate during ordinary single clicks — rather than condemn a mouse on one event. Some browsers act on the back and forward buttons before this page can see or suppress them, so a side button that navigates instead of lighting up is registering, just at a layer above the test. And buttons beyond the standard five never reach a web page at all: vendor drivers translate them into keystrokes or macros, which is a driver design choice, not a fault this test can detect.

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) at a level this page cannot intercept — the navigation fires before the event reaches the test area. The tester suppresses this where the browser allows it, but if the page still navigates, treat that as a pass: the button registered, and the browser consumed it before the test could.
What counts as a double-click misfire?
Two presses of the same button less than 80 ms apart. A deliberate double-click almost never lands that close together, but a worn switch can bounce and register a phantom second click within a few tens of milliseconds. One flag on its own proves nothing — rapid jitter-clicking can trip it — so look for misfires that keep accumulating while you make ordinary single clicks.
My mouse has extra buttons that don't register here. Why?
Web pages only see the five standard buttons: left, middle, right, back, and forward. DPI switches, sniper buttons, and thumb grids are usually handled by the vendor's driver, which remaps them to keyboard shortcuts or macros before the browser is ever involved. If an extra button is mapped to a keystroke, the keyboard tester will catch it instead.
Why doesn't the scroll count match the notches I feel?
The counter tallies wheel events as the browser reports them, and that mapping varies by device and settings. Smooth scrolling can split one physical notch into several small events, a free-spinning wheel emits a long stream of them, and touchpads report continuous motion with no notches at all. Use the counter to confirm the wheel responds in both directions, not as a notch-for-notch meter.
Can this test fix a double-clicking mouse?
No — a bouncing switch is mechanical wear, and no software can repair it. Vendor utilities sometimes mask 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