Methodology 0.2-preview

How the diagnostic works

The test records browser-observed mouse-like events only while you interact with the test surface. Raw events remain in page memory and are cleared on refresh.

What is measured

  • Complete, trusted mouse pointerdown/pointerup pairs for one button and one round.
  • Down-to-down intervals, plus click and dblclick as supplementary browser evidence.
  • Sample count, minimum, linear-interpolation median and P95.

Quality limits

Hidden pages, cancelled input, incomplete pairs, non-monotonic timestamps and reduced timer precision lower confidence. Touch and pen input are excluded. This tool cannot identify a device model, connection type or electrical switch condition.

Observation bands

The current bands are ≤ 50 ms (candidate) and ≤ 100 ms (review). They are versioned observational aids, not an operating-system double-click setting or a universal hardware threshold.

Basis for the bands

  • Mechanical switch contacts bounce for roughly 1–6 ms in published measurements, so a same-button repeat of 50 ms or less is almost impossible to produce deliberately.
  • Deliberate human double-clicks usually take 100 ms or more, so intervals up to 100 ms are marked only for review, not as confirmed faults.
  • The operating-system double-click window is a separate concept: Windows uses a default of 500 ms for the maximum interval between two intentional clicks.

Sources: Microsoft SetDoubleClickTime; OMRON chattering FAQ; Analog Devices Switch Bounce and Other Dirty Little Secrets; Texas Instruments Debounce a Switch; EEJournal Ultimate Guide to Switch Debounce; QMK debounce configuration.