Help center
Mouse test FAQ
Understand what browser diagnostics can observe, how to interpret a result, and what to try next.
Useful answers
Questions about mouse diagnostics
Can an online mouse test prove hardware failure?
No. A browser test can show the events received by a page and identify repeatable patterns. It cannot directly inspect the physical switch, encoder, sensor, cable, or wireless connection.
Why should I repeat a test?
A single unusual event can be intentional or caused by temporary software behavior. A pattern that appears across repeated sessions, browsers, or computers provides stronger troubleshooting evidence.
Does the scroll test measure physical distance?
No. Wheel delta values may be expressed in pixels, lines, or pages according to deltaMode. The test records the mode and calls values browser wheel-event units.
Is 250 ms the universal double-click limit?
No. It is the transparent heuristic used by this site. Your operating system and applications may use different settings.
Why do side buttons behave differently?
Browser navigation, device utilities, operating systems, and mouse firmware may intercept or remap auxiliary buttons. A page may not receive every physical button.
What happens to my test data?
Raw samples stay in page memory for the active session. V1 has no backend or analytics that receives mouse event streams.
Can I run the tests with a trackpad?
A trackpad may produce wheel-like events for the scroll test, but click and button behavior differs by device. Results describe the events observed, not the hardware type.
Still troubleshooting?
Run the complete mouse test, then repeat any unexpected pattern in another current browser.