How to check for unintended double clicks
- Choose the physical device and the logical button you want to observe. Primary usually means left, but system settings can swap it.
- Make single, deliberate presses inside the area. Release the button completely and leave a clear pause before the next intended press.
- Watch the press total and close-interval count. A pair appears when consecutive presses of the selected button arrive less than the chosen threshold apart.
- If a close pair appears when you intended one press, repeat under the same conditions. Then compare another application, another connection or another device.
- Use the optional 25-press series for a bounded comparison. A setting change clears the current run but retains up to two deliberately saved series with their settings; Reset clears everything.
An intentional double click can demonstrate the counter. It cannot show whether the test will catch a real, intermittent switch fault.
Press intervals and browser double clicks are different
The main counter follows button press transitions received by the browser. Each new press counts once; releases are displayed separately. Three fast presses contain two consecutive intervals, so they can produce two close pairs. The distribution covers all comparable intervals in the current run. For the unlimited free test, the median uses at most the latest 256 comparable intervals; a 25-press series fits in full.
The threshold is an exploratory setting, not a universal boundary between a good mouse and a faulty one. The initial 100 ms setting simply gives you a starting point. A higher value includes more intentional gestures; a lower value excludes some observations. Intervals use event timestamps, so a busy page does not compress queued presses into an artificially short pair. Missing, inconsistent or unusable timestamps are excluded and reported. This remains browser timing, not an electrical measurement inside the switch.
The separate browser double-click count follows the browser’s own double-click event. Its rules can depend on settings, timing, movement and button support. Two close press events do not always produce that signal, and that signal does not prove that either press was unintended.
What to do with your result
| Observation | Useful next check |
|---|---|
| No close intervals appeared | This run contained no pair below your selected threshold. Repeat the action that normally causes trouble; an intermittent issue may not happen in this run. |
| A close interval appeared after one intended press | Try spaced single presses again. Compare another application and another connection, keeping the same button and threshold for a useful comparison. |
| It happens only with a trackpad | Check tap-to-click, multi-finger and accessibility settings. Trackpad gestures do not test a physical mouse switch. |
| A button does not register, or a drag releases | Use the mouse button, hold and wheel test to separate a missing press from a hold interruption. |
| A website activates twice, but this test receives one press | Compare another website or application. Page behavior and extensions can differ; a single browser observation cannot isolate the cause. |
What this test cannot diagnose
This page observes input that reaches a browser. It cannot inspect switch contacts, firmware filtering or the user’s intention. It does not certify a hardware fault, a failure rate or a “healthy” mouse. Its ability to detect a reproducible faulty physical switch has not been validated; read our method and validation limits.
Touch and pen input are excluded from the mouse press count. A mouse and a trackpad can both appear as mouse input, so the device selector states your test setup. Browser or system shortcuts may consume events. Leaving the area, changing windows or cancelling input clears held states and the interval comparison across that interruption. A running 25-press series pauses and requires an explicit resume; its interruptions remain visible in the report.
Use this page to record and reproduce an observation, then compare contexts. If you contact support, describe the intended gesture and where you reproduced it, alongside the report.
Privacy and local reports
Counts and timing observations remain in this page’s memory and disappear when you leave or reset. Reports contain the selected settings, aggregate observations and method limits, without a click sequence or a device identifier. Downloading a report is your action and does not upload it. TinyFingers uses its existing Google Analytics for general page and tool usage; raw input and intervals are not sent. About TinyFingers and privacy.