What the result actually measures
The tester records mouse and pointer events inside the test surface. It shows which button index arrived, whether the button is held, how long it remained down and which wheel direction was reported.
Measurement boundary: A browser event does not reveal the physical cause of a failure. Driver utilities, accessibility settings, wireless links and button remapping can alter what the page receives.
How to interpret the output
Clean press and release
Each deliberate click should create a matching down/up sequence without extra changes.
Auxiliary buttons
Back/forward buttons are usually reported as additional indices, but a browser or driver may also navigate unless the focused surface can intercept them.
Wheel direction
The sign and size of wheel events can vary by OS settings, smooth scrolling and hardware.
Troubleshooting unexpected results
Side buttons navigate the page
Keep the pointer inside the test surface and try the dedicated mode. Some browser/driver combinations reserve the navigation action.
Wireless clicks disappear
Retest with a fresh battery, closer receiver, another USB port and a wired mode if available.
Frequently asked questions
Can this measure click latency?
Not physical switch-to-USB latency. It can measure intervals between browser events, which include the entire software path.
Does the test block right-click menus?
Only inside the active test surface so the secondary button can be observed.
Are mouse movements uploaded?
No. The current diagnostic session stays in the page.
