Short answer: a mouse that fires two clicks from one physical press is almost always switch chatter — the tiny microswitch under the button has worn or picked up debris, so its contacts bounce and send two electrical clicks for a single press. Before you replace the mouse, you can confirm the symptom in the browser in under a minute, and a few fixes sometimes bring a chattering switch back.
First, confirm it really is double-clicking
A double-click fault is easy to feel and hard to prove — until you look at the intervals. The double-click check records the time between button events. Click slowly and deliberately, once, and watch what it logs: a healthy button shows one press and one release; a chattering switch shows two presses a few milliseconds apart — far faster than any human could double-click on purpose. That short second event, on a click you made once, is the signature of chatter.
Be honest with yourself about the test, though: the browser sees the doubled event, not the switch. It can tell you the button is misbehaving and let you record exactly how, but it cannot open the mouse or certify which component failed. It confirms the symptom — the fix is still physical.
What causes it: contact bounce
Every mechanical switch bounces a little when it closes — the metal contacts touch, separate, and touch again in a few milliseconds. A new switch bounces so briefly that the mouse’s debounce firmware hides it. As the contacts wear or oxidize, or a speck of dust lands between them, the bounce grows longer than the debounce window can filter, and one press escapes as two clicks. That is why the problem tends to appear on older, heavily used mice, and why it often comes and goes before it becomes constant.
Fixes to try before replacing the mouse
- Rule out the software setting first. Your operating system has a double-click speed setting (Windows: Mouse properties; macOS: Trackpad/Mouse settings). A too-fast setting makes two intended clicks register as one — but it does not create doubles from a single click. If adjusting it does nothing for the chatter, you have confirmed the fault is hardware, not software.
- Clean the switch. A short burst of compressed air, or a little contact cleaner worked into the button gap, sometimes clears debris-caused bounce. It is the cheapest thing to try and occasionally the only thing needed.
- Rule out the connection. For a wired mouse, try a different USB port and, if possible, a different cable; for wireless, replace the batteries or re-pair. This does not fix a worn switch, but it cheaply rules out an intermittent connection masquerading as chatter.
- If it is under warranty, document and claim it. Capture the double-click check’s report as evidence rather than trying to describe the fault in words — our guide on reading a chatter result explains what the numbers mean.
- Replace the switch, or the mouse. If you are handy with a soldering iron, the microswitch is a cheap part; if not, a switch that chatters constantly is telling you the mouse has reached the end of its service life.
Make sure it is chatter, not a different fault
Chatter is extra clicks: one press, two events. The opposite symptom — a press that doesn’t register, or a button that feels dead — is a different failure, and you would check it with the mouse button check instead, watching for presses that never arrive. Matching the symptom to the right test keeps you from cleaning a switch that was never the problem.
What the browser can and cannot do here
The double-click check is honest about its role: it confirms the button is sending doubles, shows you the interval, and gives you a report you can keep — all real, browser-observed events. It cannot inspect the switch, measure contact wear, or certify a hardware fault for a manufacturer. For what the review threshold actually flags, see how the review threshold changes what gets flagged, and for the general limits of browser input testing, see how we test.
The short intervals this check records are real button events observed in the browser; the interpretation of them as “chatter” is a symptom, not a hardware diagnosis. The reference numbers are in the open double-click input behavior dataset. On your machine the intervals will differ — what matters is a second event appearing on a click you made only once.