Double-click & chatter test

Measure the timing of deliberate double-clicks or look for unexpectedly rapid repeats while making single presses. Intent changes how the same interval should be read.

No permission · no upload · session only

How to use

Choose whether you will intentionally click twice or make separated single presses.
Select one logical button, set both interpretation thresholds, then start the run.
Keep every press inside the target. Review each interval, not only the summary count.

Test setup

Settings lock while listening so one run uses one interpretation.

What will you do?

Intentional double-click timing Clicks are grouped 1–2, 3–4 and so on. A very fast pair is still treated as intentional, not diagnosed as chatter. Single-press chatter check Make one deliberate press at a time. Very short consecutive intervals become candidates for review, never proof of a fault.

Logical mouse button

Primary
(usually left) Middle
/ wheel Secondary
(usually right)

Interpretation thresholds

Very short repeat at or below ms Double-click window at or below ms

Current rule: ≤ 80 ms is very short; ≤ 500 ms is inside your chosen double-click window.

Configure the run, then choose “Start new run.” Clicks on setup controls are never test input.

Test target

Not listening

Run not started Start, then press inside this area Keyboard activation is not counted. Middle-button defaults and the context menu are suppressed only in this target.

Last accepted activity No completed mouse press yet

Source not observed

Bounded run summary

No interval yet

The first completed press establishes a starting point.

Completed presses 0 down → up in target

Intervals retained 0 / 60 oldest drops after 60

Last interval — real event timestamps

Median interval — retained intervals only

Very fast pairs 0 intentional in this mode

Native dblclick events 0 browser/OS signal, usually primary

Individual intervals

Newest first · maximum 60

#	Button	Interval	Interpretation
No intervals recorded.

Timing is not intent

A short interval can be a deliberate second click. Only single-press mode labels very short repeats as candidates, and only when you know you intended separate presses.

Logical, not physical buttons

Browsers report primary, middle and secondary mappings. Primary may be physically right on a left-handed setup. Driver remapping or shortcuts can stop events before this page sees them.

Evidence, not a diagnosis

This tool sees trusted browser events after device firmware, drivers and the operating system. It cannot inspect a switch, identify a mouse, prove hardware chatter or rule out an intermittent issue.

Native double-click signal

The browser decides whether to emit dblclick using OS/browser rules the page cannot read. Calculated intervals use your visible thresholds; the native count stays separate.

Touch, pen and trackpads

Touch and pen pointer contacts are excluded when identifiable. A trackpad may report mouse-compatible events and cannot always be distinguished from a physical mouse in browser JavaScript.

Interrupted runs

Leaving or hiding the page stops listening and discards any press that was still down. Existing completed intervals remain visible until you clear, reset or start a new run.