BROWSER INPUT CHECK
Mouse Double Click Test
One deliberate click. More than one response? Check what your browser receives.
Swapped your system buttons? Choose by the assigned function.
Select Start test, then click inside this area.
Aim for 30 complete cycles and 20 comparable gaps.Use a physical mouse. A touchpad can also appear as a mouse; this tool cannot reliably tell them apart.
- Complete cycles
- —
- Comparable gaps
- —
- Short-gap pairs
- —
Loading the test tool…
The test needs JavaScript to finish loading. If it stays unavailable, reload the page. The method and instructions remain readable. Reload
This result describes browser input under this run’s conditions. It is not proof of hardware health.
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.
Loading the test tool…
Compare two runs
Rule version: short-gap-v1A second run will appear alongside this one. Only the two most recent runs are kept.
Event record
Most recent 100 events. Times are browser event times, not hardware latency.
No events recorded.
A simple, repeatable check
Choose one button
Start with the button that behaves unexpectedly.
Click deliberately
Keep the pointer inside the pad and release fully each time.
Read, then repeat
Keep a second record if you change a test condition.
Before interpreting your result
Does a short gap mean my mouse is broken?
No. Intentional fast clicking, macros, drivers, and hardware behavior can all produce closely spaced input. Repeat slowly and compare conditions.
Why did the test stop when I changed tabs?
The page cannot preserve a continuous observation after losing focus. The partial record stays available, and you can begin a new run.
Can I compare a left-button run with a right-button run?
The page retains both, but they are different inputs. Use the same button for both rounds when comparing a USB port or another condition, and reach the sample target each time.
Do I need to change USB ports after every test?
No. First repeat slow clicks on the same button and port. If the symptom persists, change one available condition and record it. Two runs without short gaps do not prove the mouse is healthy, and do not by themselves require a different port.
Which devices have been validated?
This version has automated Chromium checks, including the deployed pages. Physical-mouse compatibility and fault detection have not been systematically validated. Windows Chrome and Edge are the first intended manual test environments.