Input toolsPERIPHERAL TEST WORKBENCH
Mouse test
Buttons, wheel and movement — in one workspace.
Mouse test area
Click, scroll or drag anywhere inside this area.
MEASUREMENTS
BROWSER INPUTPress and release each button. Scroll both ways, then drag.
Button state timeline
Primary button · received stateClick, scroll or move here without rotating the model.
Event register
| Time (s) | Event | Control | Raw values |
|---|---|---|---|
| No input recorded. Move your mouse into a test area to begin. | |||
These are inputs received by your browser. Touchpads may also generate pointer and wheel events. Input coverage does not certify hardware health.
How to test & what the numbers mean
Test the input you receive
Move inside the model or chart to capture input. Press and release each button, scroll in both directions and drag with the primary button. The blue highlight means held now; “Observed” means a complete down/up pair was received.
The wheel is captured only inside these areas. Use the page margins or scrollbar to read the rest of the page. Touch and pen input do not count as mouse input.
Read the evidence
Short click intervals can come from intentional double clicks. Repeat slowly before drawing conclusions. Event rate describes browser-delivered movement samples, not USB polling rate or click-to-screen latency.
Movement units depend on the browser and operating system. This tool does not estimate sensor DPI. JSON includes method, environment, retained data, interruptions and buffer limits; CSV contains the retained raw event register.
Missing input?
Browser navigation and OS shortcuts can intercept side buttons. Swapped primary/secondary settings follow browser button numbers. Ordinary web pages cannot reliably identify a mouse model or distinguish two mice and a touchpad.
Switching windows or hiding the page interrupts an active sample and clears held states without recording a false release. 3D failure does not stop measurements.