Mouse Test
Test mouse buttons, scroll wheel, and double-click online, display mouse status in real-time
Mouse Information
Event History
What is Mouse Test?
A mouse test checks whether common mouse actions are reaching the browser: left click, right click, middle click, wheel scrolling, double-clicks, and pointer movement inside a test area. It helps when a button feels unreliable, the wheel skips, double-clicks happen accidentally, or an external mouse needs to be checked before work or gaming. The tool shows coordinates, button states, event history, and scroll deltas, which helps separate hardware behavior from application-specific problems. It can confirm that the browser receives mouse events, but it does not measure DPI, sensor accuracy, polling rate, lift-off distance, or driver-level features. For those hardware-level metrics, use the mouse vendor’s software or a specialized benchmark.
How to Use
How to use
- Move the mouse within the test area to see coordinates
- Click left, right, and middle buttons to test
- Double-click the test area to test double-click
- Scroll the wheel to test scrolling
- View event history below
Tips
- The mouse visual shows button states in real-time
- The left button highlights blue, the right button highlights green, and the middle button highlights orange
- Scroll test area shows scroll distance
- Supports detection of all standard mouse buttons
Use Cases
Technical Principle
The browser surfaces mouse events through the MouseEvent interface: common types include mousedown, mouseup, click, dblclick, contextmenu (right-click menu), wheel (scroll), and mousemove. Key MouseEvent fields: button indicates which key was pressed (0 left, 1 middle, 2 right, 3/4 side); buttons is a bitmask of all keys currently held (1 left, 2 right, 4 middle, 8/16 side); clientX/clientY are coordinates relative to the viewport; pageX/pageY are relative to the document (still accurate after page scroll); screenX/screenY are relative to the physical screen. A dblclick event fires when two clicks occur within the system double-click time (Windows default 500ms) and at similar positions. The wheel event uses deltaY for vertical scroll (positive = down, negative = up), and deltaMode to express units (0 pixel, 1 line, 2 page). PointerEvent is the next-generation unified pointer event that combines mouse, touch, and pen input, with a pressure field (0-1) for stylus pressure - the future direction for mouse-style input. Mouse polling rate is how many times per second the mouse reports its position to the computer; common values are 125 Hz / 500 Hz / 1000 Hz. Higher rates make cursor movement smoother, at a small cost in CPU.
- MouseEvent.button: 0 left, 1 middle, 2 right, 3/4 forward/back side buttons; buttons is a bitmask of all currently held keys.
- dblclick condition: two clicks within the system double-click time (Windows default 500ms) at close positions.
- wheel deltaY: positive = scroll down, negative = scroll up; deltaMode distinguishes pixel / line / page units.
- PointerEvent unifies mouse / touch / pen input; the pressure field (0-1) is used for drawing tablet pressure detection.
- clientX/clientY are relative to the viewport; pageX/pageY to the document (accounting for scroll); screenX/screenY to the physical screen.
- A 1000 Hz polling rate means 1000 position reports per second, a 1 ms interval; high polling rates help cursor smoothness in FPS games.
Examples
Left-Button Click
Click in the test area -> button: 0 (left), buttons: 1, clientX: 542, clientY: 318Scroll Wheel
Scroll down one notch -> wheel deltaY: 100, deltaMode: 0 (pixel), cumulative scroll: +100Quick Double-Click
Two clicks within 200 ms -> dblclick fires, button interval 187 ms, clientX/Y delta < 5 pxFAQ
What does it test?
Left, right, middle, and side buttons (forward/back), scroll wheel, double-click timing, and pointer-position updates. Press each button to see it light up; scroll to see the wheel direction; double-click within the OS double-click interval to confirm timing.
Why isn't my middle/scroll-wheel click registering?
Some browsers intercept middle-click for scrolling and don't pass the event to the page. The test usually still detects the auxclick event (button === 1). If neither appears, your hardware switch may be failing. A loose middle-click that scrolls when pressed is also a common defect.
How does it test double-click?
It measures the time between two clicks on the same target. The browser fires a `dblclick` event when this falls within the OS double-click interval (typically 500 ms). The page shows the actual interval so you can see if your finger is faster or slower than the system threshold.
Can it detect chattering or stuck buttons?
Click once and watch the click counter. A chattering microswitch fires multiple events. The page may also show an event-log view with timestamps that makes brief double-events visible. Repair guides for common gaming mice (Logitech MX, G502, ZOWIE) usually start with this kind of test.
What's the polling rate / DPI test?
Polling rate is how many times per second the mouse reports its position to the OS. The page can estimate it by counting mousemove events while you wiggle the cursor; a 1000 Hz mouse should report ~1000 events/second of continuous motion. DPI testing requires a fixed-distance ruler and is harder in-browser - use a dedicated tool for that.
Why does my touchpad behave differently?
Touchpads emit pointer events similar to a mouse, but secondary buttons, pinch-zoom, and scroll gestures are firmware-translated and may not surface as discrete events. The test was designed for mice; trackpad results are rough indicators only.
Is anything uploaded?
No. Click and motion events are handled in your browser. Nothing is logged or sent to a server.