No unexpected repeat observed
The declared single presses, browser down signals and completed actions matched, with no native main-button double-click.
Next:Repeat only if the symptom is intermittent or limited to another app.
MOUSE INPUT DIAGNOSTIC / 02
Double click test.
Check whether one deliberate press reaches your browser more than once.
Run a paced single-press round for the button that worries you. You will get a named result, the browser events behind it, and a controlled next step. If you only want to know whether a deliberate double-click is recognized, use the separate recognition check below.
CHOOSE THE RIGHT TEST
Two symptoms need two different checks.
PRIMARY TESTOne press seems to become two
Make deliberate single presses. Compare your physical action count with the browser signals and native double-click events.
Start the unwanted-repeat check ↓SECONDARY CHECKTwo fast presses are not recognizedIntentionally double-click the main button once. Check whether this browser groups the two clicks as a native double-click.
Go to recognition check ↓UNWANTED-REPEAT CHECK
Make one press at a time.
Choose one button, declare how many physical presses you will make, then use the same steady pace for the whole round.
Count your physical presses yourself. Pause between presses and release inside the area. The browser cannot know your physical action count without your declaration.
MAIN BUTTON / TEST SURFACESTART A ROUND
Only mouse input for the selected role is counted. Touch, pen and keyboard activation are excluded. Back and Forward are tested on the complete mouse test because browser navigation can take over those buttons.
WHAT THIS BROWSER RECEIVED
Live evidence
Browser presses
Selected-button down signals in the test area.
Completed clicks
Main-button press and release recognized as a click.
Browser double-clicks
Native browser grouping for the main button.
Declared physical presses20
EVENT ORDER
See where the result came from.
Each mark is one selected-button down event in arrival order. Equal spacing is not a time scale. A quick right/middle pair is a pacing note; it does not fail the round by itself.
completed browser double / quick pair incomplete release
Show exact recent press records
- No selected-button presses recorded in this round.
YOUR ROUND RESULT
Not checked enough yet
Start and stop a complete single-press round to get a result.
Next: start the round, make the declared physical presses, then Stop.
This is a browser-observation result for the declared protocol, not a physical-switch diagnosis. Read the exact method.- Declared
- 20
- Down signals
- 0
- Completed
- 0
- Native doubles
- 0
CHECK WHETHER IT REPEATS
Change one condition, then compare A and B.
Save this stopped round, reset, and repeat the same button and physical-press count. Change only one useful condition such as the browser, USB port, receiver position, battery state, mouse or computer.
Stop a complete round to compare declared and observed input.
Saved rounds stay in this open page only. Reloading clears them.
No saved round yet. Save A, reset, change one condition, then save B.
INTENTIONAL DOUBLE-CLICK RECOGNITION
Can this browser recognize two fast main-button clicks?
This check answers a different question. Start the attempt, intentionally double-click once inside the area, then read whether the browser emitted its native primary-button double-click event.
MAIN BUTTON ONLYDouble-click hereStart the attempt first
The W3C browser event is defined for the primary button. Right and middle buttons do not receive a native dblclick result.
RECOGNITION RESULT
Not checked yet
Start, intentionally click twice quickly, then finish if the browser does not complete the attempt automatically.
- Completed clicks
- 0
- Press gap
- —
- Native double
- No
READ THE OUTCOME
What each result lets you conclude.
Unexpected repeat observed
The browser received more signals than you declared, or grouped a native double during the deliberate-single protocol.
Next:Run B with one changed condition. A repeated observation is stronger evidence than one round.
Missing or incomplete input
Fewer signals arrived than declared, or a press did not complete inside the test area.
Next:Check the selected role, release inside the area, then compare another app or connection.
Not checked enough
The round is still running, was interrupted, has an invalid plan or was stopped while a press was held.
Next:Reset and finish a controlled round before using the result.
MATCH THE NEXT STEP TO THE SYMPTOM
The same result can have different causes.
This page tells you what reached the browser. Use the context to choose the next comparison; do not jump from one result to a hardware diagnosis.
It happens in every app
Repeat with another browser, then another mouse or computer if available. A repeat across contexts is more useful than changing several settings at once.
It happens in one game or app
Check that app’s bindings, macros and single-click behavior before changing the mouse. Keep the same button and action when comparing.
A held click releases early
That is not only a double-click question. Use the exact press record here, then test hold and drag on the complete mouse test.
The issue comes and goes
Use 20 or more declared presses and save A/B conditions. A clean round does not rule out an intermittent problem.
IF INTENTIONAL DOUBLE-CLICK IS NOT RECOGNIZED
Review the operating system timing setting.
This setting changes how fast two intentional primary-button clicks must be for the operating system to recognize a double-click. It does not prove or repair unwanted extra input.
macOS
Open System Settings → Accessibility → Pointer Control, then review Double-click speed.
Apple instructions ↗Windows
Open Settings → Bluetooth & devices → Mouse → Additional mouse settings → Buttons, then review Double-click speed.
Microsoft instructions ↗MEASUREMENT BOUNDARY
The browser can observe input, not inspect the switch.
A result applies to this button, browser, page and round. The page cannot identify the mouse model, read firmware debounce, inspect electrical contacts or prove switch wear. Main-button completion uses the browser’s native click and dblclick events. Right/middle completion uses matching down/up events; the displayed 500 ms quick-pair count is only a disclosed pace note and does not decide pass or fail.
For the full event definitions and current site rules, read MouseCheck methodology.