Your mouse turns one click into two
Make deliberate single clicks, compare repeatable series, and separate extra inputs from an app’s interpretation of a click.
Updated 8 September 2026 · Observation method v2
First check what “twice” means.
A file opening after one click, a word being selected, and two button presses reaching a page are different observations. Note the action you expected and the action you saw. Then use single clicks to look for extra received inputs.
Run a comparison you can repeat
Choose one button and one input device
Use the mouse you are checking. Keep fingers off any trackpad and avoid auto-clickers or macros during the check. “Primary” describes the assigned action, which may differ from the physical left button with left-handed settings. See how browsers report button assignments.
Make slow, separate single clicks
Activate the test. Press and fully release the chosen button once, pause about a second, and repeat. Count your intended clicks. Do not deliberately double-click and do not chase the smallest interval.
Keep the first series as a reference
Start a series of 25 received presses. It ends after the 25th received press is released. Count your deliberate clicks separately: the tool cannot infer how many gestures you intended. Record that count, the threshold, close pairs and any interruptions. Twenty-five is a practical comparison length, not a certification standard or a guarantee of exposing intermittent faults.
Repeat before changing a setting
If something unexpected appears, repeat with the same button, count, pace and connection. After that, compare one changed condition, such as a direct connection instead of a hub. Do not change the threshold and connection together.
Turn the observation into the next check
- More received presses than intended clicks
- Repeat the series slowly. If the mismatch returns, reproduce the original symptom in another application, then compare another connection or compatible computer. The mismatch needs investigation; it does not identify a switch failure.
- A close pair, but the intended and received counts match
- You may have clicked faster than intended. Repeat at a steadier pace before interpreting the interval. The selected threshold labels a timing relationship, not whether your gesture was accidental.
- The app acts twice, but the test shows ordinary single inputs
- Check the app’s single-click behaviour and mouse-button assignments. Record whether the effect exists only in that app. An operating system’s double-click setting controls gesture interpretation; it does not validate the hardware.
- The button will not stay held
- Use the mouse hold check. Keep the pointer in the area, hold for about three seconds, then release. Leaving the page or losing focus makes the trial interrupted, not a demonstrated switch failure.
- No unexpected input in this run
- Record the setup and count. A short clean run does not rule out an intermittent problem; repeat when the original symptom occurs.
A double-click event is not a third click
The browser may emit a separate double-click event after its click events. Adding it to the press count would count the same gesture again. TinyFingers keeps these observations separate. MDN documents this event sequence.
The page measures browser events, not the electrical signal inside the switch. It cannot measure the mouse’s absolute hardware latency or prove that a driver, contact or cable is the cause. A busy browser or an interrupted trial can also limit interpretation; read the test’s quality notes before comparing runs.