Mouse Test: Double Click, Button Hold & Wheel Evidence
Test browser-visible mouse clicks, holds, movement and wheel events. Review event timing locally and export JSON or CSV evidence for comparison.
Mouse Evidence Lab
Use a physical mouse in a foreground browser window. Press Start inside the resulting lab; the form alone does not begin recording.
Supported scope: 2 minutes / 5,000 events · five browser button roles · local JSON baseline ≤1.5 MB · no electrical switch diagnosis, DPI, polling-rate or hardware latency measurement.
Your inputs
Required fields are marked with an asterisk.
Your result
Review your output, then save it to your device.
Make the next step clear.
Your findings, assumptions and next steps will appear here after you run the check.
Mouse Evidence Lab · https://mouse.kitforma.com/ · KitForma
Focused local capture
Explicit evidence limits
JSON and CSV comparison
Understand the evidence.
Focused guides explain the rules, the edge cases and the checks worth doing before you act.
Investigate unwanted mouse double-clicks
Use slow single presses, a clear review window and an exportable event sequence.
Read the guide ↗Field guide / 02Test mouse button holds without inventing release times
Separate completed short holds, incomplete holds and deliberate early releases.
Read the guide ↗Field guide / 03Read wheel and movement evidence correctly
Preserve wheel units and avoid confusing an on-screen path with physical measurements.
Read the guide ↗Before you start
Does a rapid repress prove my mouse double-clicks?
No. The lab flags a new down event soon after a release of the same logical button. Fast intentional clicking can produce the same sequence. Repeat slow, separated single clicks and keep the timestamps as evidence; the browser cannot isolate a switch fault from firmware, the OS or input software.
How does the hold test work?
Choose a requested hold duration, start a fresh session, then deliberately hold and release a button. Completed holds below that duration are highlighted. An intentional short release also qualifies; a held button when capture stops is shown separately and is not assigned an invented release time.
Is a browser double-click event the same as switch bounce?
No. The browser reports dblclick using its own and the operating system’s click interpretation. The report counts these events separately from down/up timing. Neither signal by itself establishes an electrical cause.
Why does the wheel report have three groups?
WheelEvent.deltaMode distinguishes pixel, line and page units. Adding them together would create a misleading total. The report preserves horizontal and vertical deltas in their original unit groups; these are browser scroll requests, not physical wheel distance.
Does the movement chart measure DPI?
No. It draws normalized pointer positions inside the test area. Browser scaling, pointer acceleration, display scaling and sampling affect that path. It cannot measure physical travel, sensor DPI, polling rate or hardware latency.
What is stored or sent?
Capture records relative times, logical button numbers, normalized local positions and wheel values only inside the active test area. It uses no automatic storage or device identifiers. JSON and CSV stay local until you share them. Clear removes the current session and baseline. General site analytics do not receive event records.
Sources & assumptions
Formats, algorithms and supported features are documented below. Check the stated scope and inspect your output before using it.
- MDN: MouseEvent.button ↗
Logical button roles may be remapped by the user or OS.
- MDN: WheelEvent.deltaMode ↗
Wheel values can use pixel, line or page units.
- W3C UI Events ↗
Mouse event and double-click behavior.
Reviewed 2026-10-19. Read our methodology or report an issue.