Mouse test

Move the pointer into the test area to begin. Click each mouse button, including the middle button and any side buttons, and scroll the wheel. The page records button presses, how long you hold a button, and the wheel movement it receives.

The test checks buttons 0 to 4: left, middle, right, back and forward. Side buttons are included as back and forward when the browser reports them. The page suppresses the context menu and back navigation only inside the test area, so those actions do not interrupt the check there.

Button readings show which button the page received and its press count. Hold time shows how long you kept a button pressed. Click and hold each button to see whether the page registers the action and whether the hold time changes while you keep it down.

Wheel readings show the steps the page received, the scroll direction, and any tilt reported by the wheel. Scroll in both directions and compare the readings. The displayed movement describes what the browser received; it does not show how the mouse is built or how much physical distance the wheel turned.

The event-rate estimate is labelled “events the browser received per second.” It counts pointer events delivered to the page over time. Where available, the test uses the browser’s raw pointer updates; otherwise it uses grouped pointer events. Treat this as an estimate of the browser’s event rate, not the mouse’s USB polling rate.

If a button does not register, the page may not be receiving that button’s event. Check whether the same button works elsewhere, then reconnect the mouse or try another connection if available. If a side button triggers back or forward outside the test area, that is outside the area where this page suppresses navigation.

If the wheel does not register steps, or direction seems wrong, scroll slowly in both directions and check whether the readings change. A missing tilt reading may mean the page received no tilt event. If the event-rate estimate is absent or changes, it may reflect which pointer events the browser supplied; it is not a direct reading of USB polling rate.

If the same control still fails here and elsewhere, check the mouse connection and device settings, or try the mouse on another device to narrow down whether the issue follows the mouse.

The page can show whether the browser receives clicks, holds, wheel movement and pointer events in this test area. It can help you separate a button that is not registering from a wheel that is not reporting movement.

The readings do not identify the cause of a problem. A missing event could come from the mouse, its connection, device settings or the way the browser reports input. The event-rate estimate is about events received by the page, and it does not establish a mouse’s USB polling rate.