Short answer: yes, you can find out in under a minute, right in the browser, without installing anything. Open a double-click check, click once, slowly and deliberately, and watch what it logs. A healthy button records one press and one release; a faulty one records two presses a few milliseconds apart from that single press. That second event, on a click you made only once, is the answer.
The 60-second check
- Open the double-click check — it runs in the browser, nothing to install.
- Click the affected button once, slowly and on purpose. The point is to make exactly one press so any second event is the mouse, not you.
- Read the log. One press and one release means the button is behaving. Two presses only a few milliseconds apart — far faster than any human could double-click intentionally — means the button is sending doubles.
- Repeat a handful of times. Chatter is often intermittent early on, so a fault that appears on one click in ten still counts.
How to read a “yes”
The tell is the interval. A deliberate human double-click lands somewhere in the range of a couple hundred milliseconds between clicks; a chattering switch fires its second event within a few milliseconds. So if you pressed once and see two clicks separated by single-digit milliseconds, that gap is too short to be you — it is the switch bouncing. The numbers on your machine will differ from anyone else’s; what matters is a second event turning up on a press you made only once.
What a “yes” usually means
A single press that registers as two clicks is almost always switch chatter — the microswitch under the button has worn or collected debris, so its contacts bounce and send two electrical clicks. It is a hardware wear pattern, which is why it shows up on older, heavily used mice. Some of it is fixable without a new mouse; the steps are in our guide on how to fix a mouse that double-clicks.
What this check can and cannot tell you
Be clear about what the browser actually sees. It observes the doubled event — a real, timestamped click your browser received — and it lets you record the interval. What it cannot do is open the mouse, measure the switch, or certify which component failed. It confirms the symptom and gives you evidence of it; the diagnosis of a worn switch, and the fix, are still physical. The general limits of browser input testing are laid out in how we test.
If the check says no — or shows a different fault
If a single click logs a single event every time, the button is not chattering, and a “double-click” feeling may be the operating system’s double-click speed setting instead — that turns two intended clicks into one, but it does not create doubles from one press. The opposite symptom — a press that never registers, or a dead button — is a different failure you would look at with the mouse button check, watching for presses that never arrive.
Keep the result
If the button is failing and it is under warranty, the recorded intervals are far better evidence than a description in words. Our reference on reading a chatter result explains what the numbers mean and how to present them for a claim.
The short intervals this check records are real button events observed in the browser; reading them as “chatter” is a symptom, not a hardware diagnosis. The open double-click input behavior dataset lists the reference numbers. On your machine the intervals will differ — what matters is a second event on a click you made only once.