Mouse switch debounce, double clicking and CPS
By Mihai
Use deliberate interval tests to investigate repeated presses, and keep that question separate from clicking speed.
One physical action can have a complicated path
A mouse button actuates a switch, device firmware interprets the contact, and input travels through the operating system to the browser. The page observes pointer events after those stages. Contact behavior, debounce, driver settings and synthetic actions can all influence what appears. A web page cannot examine raw switch voltage or determine the mechanical condition of a device from one short session. Its useful contribution is a clear record of observed intervals under deliberate conditions.
Debounce is an interpretation step
Switch contacts can change state several times around an actuation, and a debounce process attempts to treat that transition as one intended action. The implementation can live in firmware or software and its timing differs by device. Aggressive suppression can hide rapid transitions; a permissive configuration can expose more events. This guide does not recommend a universal debounce setting. Record the setting you actually use when comparing observations, and consult the device’s own documentation for supported configuration.
Why this tester highlights eighty milliseconds
The interval panel marks consecutive initial presses below 80 ms as short. That value is a heuristic chosen for inspection, not a statement that every short pair is a broken switch. Deliberate fast clicking can generate the same pattern. To investigate an unintended repeat, make one isolated press approximately each second and watch for an extra event you did not intend. Repeated observations under that condition are more informative than a red warning produced while intentionally clicking as quickly as possible.
CPS answers a different question
Clicks per second divide accepted presses by a time window. A one-second burst and a sixty-second endurance run use the same arithmetic but different tasks. The first press counts in Void Fabric’s window. A high CPS can depend on technique, hardware or generated input and is not a certificate of gaming skill. During speed practice, short intervals are expected. During interval inspection, slow controlled presses help distinguish the intended action from an unexpected additional event. Keep those two experiments separate in your notes.
Make a useful fault report
Describe the device, connection, application, click pace and whether the behavior repeats in more than one setting. A second pointer or another connection can help isolate a pattern, but change one variable at a time. Check for macros, accessibility settings or software that intentionally modifies clicks before blaming a mechanical switch. A clean session cannot rule out an intermittent problem, and a short interval alone cannot establish one. The local session summary preserves the number of observed short intervals; it does not upload a hardware report.