What the Rapid Trigger Test Measures
The test calculates key-down duration from keydown to keyup, reset gap from keyup to next keydown, and full cycle from one keydown to the next. Medians describe the typical observed cycle; median absolute deviation describes variation.
Run labels such as Rapid Trigger ON and Baseline are chosen by you. The test cannot read the keyboard setting.
How to Use the Rapid Trigger Test
- 1Choose W, A, S, D, Space or a custom physical key.
- 2Set the keyboard configuration and label the run.
- 3Perform 20 consistent press-release cycles.
- 4Note the median reset gap and variation, then change only the setting you want to compare.
- 5Repeat with the same browser and similar finger motion.
How to Interpret the Result
A shorter observed reset gap in one run does not prove a better physical reset point. Finger motion, firmware, the operating system and browser scheduling all contribute.
Compare medians and variation across repeated runs rather than a single fastest cycle.
Comparing Two Keyboard Settings Fairly
Choose one physical key and complete 20 consistent cycles with the first keyboard setting. Note the median reset gap and Reset Variation (MAD), save that run in the page, and then change only the setting you want to compare. Use similar finger movement, posture and system load for the second run.
The ON, OFF and baseline names are user-selected labels. InputMetric does not read the keyboard's control software or firmware state. If the second run changes, the observed intervals changed; the result alone cannot isolate whether that difference came from the keyboard setting, your motion or event scheduling.
Why Distance Cannot Be Derived From Timing
A keyboard event tells the page that a logical key state changed. It does not include magnetic sensor position, physical travel or a millimeter value. Even very consistent browser event gaps therefore cannot be converted into a physical actuation or reset distance.
Missing keyup events and tab visibility changes invalidate an unfinished cycle. Held-key auto-repeat is ignored. A full cycle is recorded only after a down, an up and the next down for the selected key have all arrived in order.
Browser Limitations
KeyboardEvent does not expose actuation distance, magnetic position, firmware scans or switch reset distance in millimeters. This is browser-observed key event timing only. Missing releases, auto-repeat and visibility interruptions invalidate a cycle.