GEARCHECK LABInspect movement and buttons from a trackball using the browser pointer stream. Trace slow paths in all directions and compare runs without assuming the page can identify the physical ball or sensor model.
Move the trackball cursor here.
Button indices are shown after presses.
Escape stops capture.
No events recorded yet.
Travel adds straight-line distances between consecutive pointer events in CSS pixels. Directional coverage records left, right, up and down movement larger than one pixel; it is a checklist rather than an accuracy score. Button indices are the values delivered by the browser. Leaving the test area breaks the path so re-entry does not create an artificial long jump. The on-screen marker follows the observed cursor position.
This tool cannot reliably distinguish a trackball from an ordinary mouse producing the same pointer events. Acceleration, cursor sensitivity, screen edges and event coalescing influence the sample. CSS-pixel travel is not physical ball distance, DPI, raw sensor resolution or certified hardware polling. Touch and pen movement is identified separately instead of being silently treated as trackball input. Repeat suspicious dropouts in another browser and connection mode.
No. The browser sees cursor movement after operating-system processing. It does not know how far you rolled the physical ball.
Diagnostic data is processed locally in this tab and is not intentionally sent to analytics. Network tools send only their test probes and temporary payloads to GearCheck Lab’s speed-test server. Media and device access starts only after your explicit action and any required browser permission. Downloaded results stay on your device.
Read the privacy policy and testing methodology. If something fails, report the tool URL and visible message.