Browser mouse check

Test mouse buttons, wheel, movement, and hold.

Use the test pad to see the logical mouse events this browser receives. It checks useful browser behavior without pretending to measure DPI, polling rate, or hardware latency.

Runs in your browserNo movement uploadNo account needed

Mouse test workspace

StatusReady — use the test pad when you want to begin.Context, wheel, and auxiliary defaults are suppressed only inside the pad when the browser allows it.
Button presses0
Double clicks0
Wheel events0

Observed buttons

Logical roles
Primaryusually left0
Middlewheel click0
Secondaryusually right0
Backif exposed0
Forwardif exposed0

Active test pad

Click, scroll, and move here.

Try primary, middle, secondary, and side buttons. Scroll in any direction. Browser/driver shortcuts can still intercept some side-button actions before a page receives them.

Hold & drag continuity

Hold the primary button here, move while still holding, then release.

Waiting for primary-button hold

Current browser facts

Last button
Held now
None
Pointer type
Wheel direction
None yet
Wheel X / Y
0 / 0 pixels
Click interval

Recent mouse events

Latest 20

    Movement coordinates and precise event timestamps are not retained in this list. The click interval is informational only, not an operating-system setting or latency measurement.

    How to use it

    One pad for the checks that belong together.

    1. 01

      Check each button

      Press the buttons you actually use. BeanNest reports browser logical roles, so Primary is usually left and Secondary usually right, but your system can swap them.

    2. 02

      Scroll and double-click

      Use the wheel vertically or horizontally, then double-click. The browser reports wheel units as pixels, lines, or pages; BeanNest keeps that unit visible.

    3. 03

      Hold, move, release

      Use the Hold & drag area to check whether the browser continues to observe the primary button while the pointer moves.

    What the result means

    Primary does not always mean physical left.

    Web browsers report logical button roles. A left-handed operating-system setting can swap the primary and secondary physical buttons, so BeanNest labels the roles instead of making a hardware assumption.

    Wheel numbers need their unit.

    A browser can report wheel deltas in pixels, lines, or pages. The test shows the browser's unit beside the latest X/Y values instead of turning unlike units into a fake universal score.

    Your movement data stays local.

    BeanNest does not upload mouse button details, pointer coordinates, movement deltas, wheel deltas, click intervals, hold duration, or the local event history. The crosshair position is an ephemeral visual aid inside this page.

    Why does a side button navigate or not appear?

    Mouse software and browsers can map Back/Forward before a page receives a cancelable event. BeanNest suppresses defaults only inside the test pad when the browser exposes them, so testing another browser or reviewing your mouse-driver mapping can help.

    What does the double-click count mean?

    It counts the browser's dblclick events. The displayed interval between recent primary clicks is only a clue; it is not your operating-system double-click threshold and it is not hardware latency.

    Can this measure DPI or polling rate?

    No. This page is deliberately focused on reliable browser-observed button, wheel, movement, and hold behavior. DPI calibration, USB polling claims, and hardware latency need different measurement assumptions and are not certified here.

    Can I test with a touchscreen?

    The page remains readable on a phone, but touch and pen input are not counted as mouse presses. Use a mouse or trackpad for the active diagnostic.

    Keep checking

    More device checks