BROWSER INPUT CHECK
Mouse Double Click Test: Method & Limits
Learn how the test counts press-release cycles, flags gaps up to 50 ms, and compares two runs. Understand sample targets, interruptions, and timing limits.
A complete press cycle
One press followed by one release of the selected logical button counts as one cycle. Browser click and double-click notifications are not counted again. Choose the assigned primary or secondary function if your system buttons are swapped. Touch and pen input are excluded; a touchpad can still appear as mouse input.
The 50 ms observation rule
The interval runs from a release to the next press, not from one press to the next. A gap must be greater than zero and at most 50 ms to be marked for review. Exactly 50 ms is included. This is an engineering threshold, not a hardware health standard or a measurement of switch debounce time.
Enough to summarize this run
The target is 30 complete cycles and 20 comparable gaps, within 60 seconds. A run stops at the time limit or 1000 cycles. Only valid adjacent cycles supply comparable gaps. The sample targets are not a statistical confidence level; an empty or small sample cannot establish a passing result.
What makes two runs comparable?
Use the same button and rule, reach the sample target in both rounds, and note which condition you changed. The page shows different buttons side by side but does not treat them as a direct comparison. An interrupted run, limited timing, or different sample sizes also limits what you can conclude. A lower count alone does not prove a repair.
Interruptions and browser timing
Changing tabs, losing focus, or breaking a press-release sequence stops continuous sampling and keeps the partial record. It does not indicate a faulty mouse. If event times cannot distinguish gaps under this rule, the result says timing is limited. Retry in a supported browser with default settings; do not disable privacy protections to obtain a result.
What a browser test cannot establish
The browser sees input passed on by the system. Firmware filtering, event timing precision, and intermittent symptoms can affect the record. No short gaps in one run do not establish that the device is healthy. This is not a CPS, polling-rate, debounce-time, or hardware-latency test, and it does not change system double-click settings.
Your test record stays here
Press events, intervals, notes, and reports are processed in your browser without being uploaded. Only the two latest runs are kept in persistent browser storage, shared by tabs for this site, until you clear or replace them. Clearing site data or using another browser profile, address, or port can make them unavailable. No sign-in is required.
The two latest runs and notes are saved in this browser for this site. They survive switching away, reloading, reopening the page, and a local server restart at the same address. Clear both runs removes them from all tabs.