Mouse test

Check the browser events produced by your buttons, wheel and pointer movement, including press-and-release delivery and extra reported buttons.

No permission requests · runs in this page

How to use

Point inside the test surface. Press and release primary, secondary, middle and side buttons one at a time.

Double-click with the primary button, move around, then scroll vertically and horizontally if your device supports it.

Confirm every press returns to “Released,” and compare counts with the bounded event log. Reset before another run.

Test surface

All reported buttons released

Click, hold, move and scroll here The context menu and page scrolling are suppressed only in this surface. Keyboard actions are not counted as mouse events.

Last test activity Waiting for browser input

Source not reported yet

Completed cycles 0 matched down → up

Browser clicks 0 a double-click includes 2 clicks

Browser double-clicks 0 OS/browser timing rule

Move event delivery 0 events latest gap —

Wheel delivery

Vertical events Up 0 · Down 0 Last ΔY —

Horizontal events Left 0 · Right 0 Last ΔX —

Delta unit: —. Counts are browser events, not wheel notches.

Excluded pointer contacts: Touch 0 · Pen 0 · Other 0

Button press and release

Browser button 0 Primary Untested Down 0 · Up 0 · Cycles 0

Browser button 2 Secondary Untested Down 0 · Up 0 · Cycles 0

Browser button 1 Middle / wheel Untested Down 0 · Up 0 · Cycles 0

Browser button 3 Back Untested Down 0 · Up 0 · Cycles 0

Browser button 4 Forward Untested Down 0 · Up 0 · Cycles 0

Additional numeric buttons reported by the browser will appear below. Driver macros and OS shortcuts may never reach the page.

Recent event log

Newest first · 0/40 entries

No events logged yet.

What the browser can tell you

This page observes trusted, logical browser events after OS and driver mapping. “Primary” may be physically right on a left-handed setup. Side buttons can be remapped to keys, macros, Back/Forward actions, or blocked before a page sees them.

What it cannot prove

A page cannot identify a physical mouse, separate multiple mice, or verify hardware polling rate, DPI, switches or wheel notches. Wheel events do not expose whether they came from a wheel, touchpad or another equivalent device. Touch and pen contacts are shown only as excluded input.

Interpreting held states

A button held for 3 seconds is marked “Release to verify”; that is a reminder, not a fault verdict. If focus leaves the page before mouseup arrives, the state becomes “Release not observed” instead of claiming the button is physically stuck.

Timing and wheel direction

Move gaps measure browser event delivery and can be coalesced, delayed or throttled. They are not hardware polling rate. Wheel signs describe intended page direction; natural scrolling, Shift-scroll and driver settings can change how a physical gesture maps to each axis.