Begin with a controlled routine
Open the lab in a foreground browser window. Select deliberate single clicks, choose a review window and prepare the lab. Start a fresh session, then click slowly inside the capture area, releasing fully and pausing between presses. This creates a sequence that is easier to interpret than a rapid clicking game.
The tool records logical button roles. Button zero usually means the primary action, but users can remap buttons. Do not infer a physical left-side switch merely from its numeric role. Compare the role you deliberately used with the down and up counts in the report.
Distinguish the observations
A rapid repress candidate is a new down event close to the same button’s previous up event. The selected interval determines which events are flagged. It is a review threshold rather than a universal failure boundary. A fast intentional double click can produce exactly the same timing pattern.
Browser double-click events are counted separately. They describe how the browser and operating system interpreted the interaction, while the down/up sequence preserves individual observations. Duplicate down events and releases without a recorded down are listed rather than silently repaired.
Keep comparable evidence
Stop capture before changing USB ports, applications or settings. Download JSON to preserve both the settings and complete sequence, or CSV for a spreadsheet. Use the stopped session as a baseline and repeat the same deliberate routine after a change.
The comparison marks whether source type, protocol and thresholds match. Even matching settings do not control every external factor. These records can support a troubleshooting conversation, but they do not identify a particular electrical component or guarantee that a device is healthy.