Use this full mouse test when you need one place to confirm that pointer movement, logical left/middle/right presses and wheel direction reach the browser. It also shows browser-pixel travel and a rolling count of delivered movement events. Those readings are a broad first check—not a hardware polling-rate, DPI or switch-certification result.
| Live reading | Useful for | Important limit |
|---|---|---|
| Cursor X / Y | Confirming that browser pointer coordinates change across the page. | Coordinates are viewport positions, not raw sensor counts or physical desk distance. |
| Left, middle and right clicks | Checking whether each logical button press reaches the test area. | One counter mismatch is not enough to identify switch wear, debounce behavior or the failed internal part. |
| Wheel steps | Confirming browser wheel events and whether reversing direction changes the signed total. | The broad total does not preserve individual reversal timing; use the focused wheel test for unexpected jumps. |
| Events per second | Comparing browser-delivered movement activity under the same conditions. | It is not a certified mouse polling rate. Event coalescing, motion, OS handling, display cadence and load affect it. |
| Distance in px | Comparing total browser-coordinate travel within one resettable session. | CSS pixels are not centimetres, raw counts or DPI. Acceleration and pointer processing can affect the path. |
The page observes events after mouse firmware, the USB or wireless connection, drivers, operating-system pointer processing and browser behavior. It cannot read the optical sensor, switch contacts, configured firmware DPI, raw USB reports or wireless radio quality directly.
Touchpads and accessibility devices can generate compatible mouse events, so a moving counter does not prove which physical device produced the input.
It can show that the browser received more logical presses than expected, but the full page does not time same-button intervals. Repeat the symptom with the focused Double-Click and Chatter Test before drawing a hardware conclusion.
No. It counts mousemove events delivered to the page during a rolling one-second window. Browser coalescing, movement speed, operating-system input handling, display cadence and load can all affect it.
The lab suppresses the context menu inside its mouse visualization so the logical secondary button can be counted. Elsewhere, the browser keeps its normal right-click behavior.
No. Distance is accumulated from browser pointer coordinates and is shown in CSS pixels. Use the separate DPI estimator with a measured physical path for a repeatable estimate.
Browser mouse events consistently cover the common logical buttons, but vendor layers, operating-system shortcuts and browser navigation can intercept or remap extra controls. Use vendor software to inspect features the page cannot see.
No. It means the checked browser-visible inputs behaved as expected during that session. Intermittent faults, firmware behavior and signals the browser cannot access may still require another computer or manufacturer diagnostics.
LOCAL INPUT: Pointer coordinates, click counts, wheel steps and movement timing are processed in the browser for this diagnostic and do not need to be uploaded for the test to function. Reset clears the displayed session counters.
GearCheck Lab does not change mouse firmware, DPI, debounce settings, operating-system pointer speed or button mappings.