Mouse Diagnostic Test

The Buttons stage records logical mouse-button events that reach the test surface. Left, right, and middle are the common controls; Back and Forward are optional because many mice do not include them and software can reserve or remap them. The Click timing stage measures intervals between deliberate left-button presses. It marks pairs below 150 milliseconds using a visible heuristic, but a close timestamp is not proof of electrical switch bounce or a faulty button.

The Movement stage summarizes pointer events dispatched by the browser. Its event-per-second estimate describes browser-observed delivery after the operating system and browser have processed input. It is not the mouse's USB polling rate. The two scroll stages calibrate direction from each local sample, then inspect opposite signs, unusually large deltas, and long timing gaps relative to the captured sequence. These clues describe the event stream, not the internal wheel encoder.

Begin with the mouse on a stable surface and close overlays that could intercept clicks. Press every available button once or twice. During Click timing, use a relaxed single-click rhythm rather than trying to click quickly. During Movement, make smooth loops throughout the card without stopping at an edge. A short movement trace can be reported only as insufficient because startup scheduling and a handful of events do not support a stable browser-rate summary.

For Scroll direction, capture Down first, wait until free-spin or touchpad inertia has ended, and then select Up. The diagnostic calibrates each phase independently so a natural-scrolling preference does not create a false universal sign assumption. In Scroll consistency, use only one direction and avoid rocking the wheel. If you accidentally reverse, start the workflow again or treat that section as contaminated rather than explaining the candidate after the fact.

Input detected means the page received at least one matching logical button event. No event captured is more limited: the action may not exist on the device, may be remapped, may have been intercepted, or may not have reached this browser card. Check focus, repeat the press, and compare the detailed mouse test. For an absent middle press, remember that wheel rotation and wheel click use different browser event families and can behave independently.

Repeated close click pairs means two or more intervals fell below the page's 150 ms heuristic in the current sample. It does not diagnose the switch. Repeat with slower intentional presses, inspect operating-system double-click preferences, temporarily review macros or vendor profiles, and compare a simple desktop application. One isolated close pair calls for more data; a sample with fewer than eight presses is explicitly too small for useful interpretation.

A usable movement sample can help compare the same setup before and after a setting change. It cannot be compared directly with a manufacturer's advertised polling rate because pointer dispatch may be coalesced, scheduled, throttled, or affected by rendering. Keep browser, connection mode, power state, and motion style constant. A lower event rate in one short run may simply reflect slower hand movement, so repeatability matters more than the largest number.

For direction and consistency, no obvious reverse-event pattern detected means the controlled browser sample met its minimum and did not show the configured repeated-opposite rule. It is not a health certificate. Repeated opposite-direction events, large-delta candidates, or long gaps deserve a controlled retest using the dedicated scroll jump and reverse tools. The diagnostic cannot observe a physical notch for which no browser event was created.

If only one section looks unusual, open its detailed tool instead of repeating unrelated stages. Use the mouse double click test for per-button interval controls, the mouse polling rate test for a longer movement trace, and the mouse scroll jump test for direction, magnitude, and timing candidates. If several input types disappear together, review connection stability, wireless power, USB routing, remote-session behavior, and application focus before concentrating on one switch or encoder.

Compare the symptom in another browser and a native application. Browser-only behavior suggests extensions, permissions, focus, or browser configuration; behavior in one program suggests that program's bindings or profile; system-wide behavior justifies checking operating-system settings, official device software, and another suitable port or device. Follow manufacturer safety and warranty instructions for cleaning or service. This mouse diagnostic test does not authorize disassembly or identify a mechanical cause.

Raw clicks, pointer events, wheel values, and the generated report remain in page memory. The workflow does not upload them, assign a device identity, or add a fingerprint. The displayed date and time are generated locally only when the report is built. Starting over clears the active diagnostic state. The workflow intentionally omits a user-agent fingerprint because it is not necessary to interpret the sample.

Use the report as a checklist for what was observed in this session. A browser cannot directly inspect the physical switch, encoder, radio link, driver queue, or USB transaction schedule. It also cannot prove why an expected event is missing. Save neutral notes about environment and repetition, then seek official or qualified support if a reproducible system-wide problem remains.