Mouse Test
Use this online mouse tester to check buttons, side buttons, held states, wheel events, and pointer movement. See browser counts, hold times, movement path, and session status.
- Direct browser input
- No device permission
- No test result history
- No account or upload
Important
- Browser Pointer Events expose logical button roles and software mappings. Touch/pen input, side-button interception, and wheel delta units can differ by device, operating system, and browser.
Ready — press Start before using the test surface. Input here is not recorded yet.
Primary / Left
button 0
Not observed
↓0 ↑0
Last hold: —
Auxiliary / Middle
button 1
Not observed
↓0 ↑0
Last hold: —
Secondary / Right
button 2
Not observed
↓0 ↑0
Last hold: —
Back / X1
button 3
Not observed
↓0 ↑0
Last hold: —
Forward / X2
button 4
Not observed
↓0 ↑0
Last hold: —
Results
- Buttons observed
- 0 / 5
- Vertical wheel
- Not observed
- Horizontal wheel
- Not observed
- Session
- Ready
- Buttons held now
- None
- Last button event
- —
- Pointer type(s) observed
- —
- Move events
- 0
- Path distance
- 0 px
- Max jump
- 0 px
- Vertical wheel events
- negative 0 · positive 0
- Horizontal wheel events
- negative 0 · positive 0
- Wheel ΔY
- —
- Wheel delta unit
- —
- Interruption
- None seen
Mouse pointer events only
Optional and absent on many devices
Browser/CSS coordinate distance
Largest browser-coordinate step
Button coverage counts only Primary, Auxiliary, Secondary, Back, and Forward roles received from a browser event identified as a mouse. It is descriptive coverage, not a pass/fail result. Side buttons and horizontal wheel input are optional and can also be remapped or intercepted.
Movement path and max jump are browser/CSS coordinate observations, not physical travel distance, DPI, polling rate, sensor counts, or sensor accuracy. A large jump can reflect fast movement, event coalescing, leaving and re-entering the surface, OS behavior, or browser scheduling.
WheelEvent deltas are browser-reported values. Their units follow deltaMode: 0 is pixels, 1 is lines, and 2 is pages; they are not physical wheel notches.
Need a focused mouse check?
- Double-Click Test →
Unexpected duplicate clicks or repeat-click interval screening.
- Scroll Wheel Test →
Wheel direction, opposite-direction events, deltas, and deeper wheel behavior.
- Mouse DPI Test →
Browser-observed DPI/CPI estimation over measured physical travel.
- Mouse Polling Rate Test →
Browser-delivered movement event-rate evidence.
Recent button & wheel events
No button or wheel events yet.
This list is session-only and shows recent browser button and wheel evidence. Pointer movement is summarized above and is not logged here.
How to use
- Press Start and keep the pointer inside the test surface.
- Press Primary/Left, Auxiliary/Middle, Secondary/Right, and any Back/Forward side buttons your device exposes. Each card shows held and observed browser events.
- Hold and release buttons to inspect browser-observed hold duration, and move or drag inside the surface to see the movement path.
- Use the wheel for a basic browser WheelEvent check. Review negative/positive vertical and horizontal deltas plus the current delta unit.
- Press Stop to freeze the session. Use the dedicated Double-Click, Scroll Wheel, DPI, or Mouse Polling Rate tools when the problem needs deeper timing or measurement.
What the result means
- Mouse and Pointer Event button codes describe logical browser roles: Primary is usually left, Auxiliary usually middle, Secondary usually right, and 3/4 are typically Back/Forward. Physical placement and software mappings can differ.
- Held now means the page received pointerdown without a corresponding release or cleanup in the active session. Observed this session means at least one browser button event reached the page; neither is hardware health certification.
- Buttons observed counts the five standard logical roles only when the browser identifies the pointer event as mouse input. Touch and pen events remain visible evidence but do not increase this physical-mouse coverage summary.
- Down/up counts are browser events, not physical switch electrical transitions. The last hold duration is browser time from pointerdown to pointerup.
- Movement path and max jump use browser/CSS coordinates. Wheel values come from WheelEvent and its deltaMode units; Stop freezes the current session.
Limitations
- Browser button roles can be remapped by OS, accessibility settings, drivers, or vendor software.
- Back/Forward buttons may be intercepted or mapped to browser navigation or macros before a standard page event is available.
- Touch and pen pointer contacts are not equivalent to physical mouse-button testing. A touch contact can appear as a primary-button-style pointer event.
- Trackpads and gesture devices may expose different button and wheel patterns than a discrete mouse.
- Horizontal wheel input is optional and absent on many mice. Not observed is not a failure result.
- Wheel delta values are browser events measured in pixels, lines, or pages according to deltaMode; they are not physical wheel notches.
- Movement path and max jump are browser-coordinate observations, not DPI, polling rate, sensor accuracy, or physical distance.
- A missing browser event does not by itself prove a broken switch or mouse.
Troubleshooting
- Right click opens a context menu
- Press Start and use the active test surface. The page suppresses the context menu inside the running session, not globally.
- Back or Forward side buttons do not register
- Vendor software, drivers, the operating system, or the browser may remap or intercept those buttons. Retry with the pointer inside the test area and compare another browser or default mouse-button mapping before assuming hardware failure.
- Touching the screen lights the primary button
- Touch or pen Pointer Events can resemble primary pointer contact. Use a physical mouse or mouse-like trackpad for a mouse-button check.
- The wheel direction looks reversed
- Wheel delta signs reflect browser and OS event semantics and can differ with Natural Scrolling or trackpads. Use Scroll Wheel Test for a dedicated direction diagnostic.
- The path shows a large jump
- Fast motion, browser scheduling, event delivery, or leaving and re-entering the surface can create a large browser-coordinate step. Repeat before treating it as a device problem.
Related tools
FAQ
Which mouse buttons can this browser test see?
Standard browser button codes commonly cover Primary/Left (0), Auxiliary/Middle (1), Secondary/Right (2), Back/X1 (3), and Forward/X2 (4), but software and OS mappings can change what the page receives.
Why do my Back or Forward side buttons not register?
Vendor remapping, macro assignment, OS or browser interception, and device limitations can prevent a standard page event. This page does not make a hardware-failure verdict.
Does a missing mouse-button event mean the mouse is broken?
No. Retest focus, mapping, browser, and device conditions before drawing a hardware conclusion.
What do Wheel ΔY and deltaMode mean?
deltaY is the browser wheel delta; deltaMode determines whether the units are pixels, lines, or pages, not physical notches. For deeper direction and wheel diagnostics, use Scroll Wheel Test.
Which mouse test should I use?
Use Double-Click Test for unintended repeated clicks and interval timing, Scroll Wheel Test for deeper wheel diagnostics, Mouse DPI Test for a browser DPI estimate, and Mouse Polling Rate Test for browser movement event rate. This page is the broad standard-button, held-state, basic-wheel, and pointer-event check.