A received down/up sequence proves the complete keyboard-to-browser path delivered that event.
IP-KEY-01 / KEY / CODE / LOCATION
Keyboard Chatter Test
Flag same-key down events that reappear within 50 ms after a release.
One physical press types two or more characters.
This focused entry uses the shared Keyboard protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
01
Match the visible layout, focus the test surface and close shortcut-heavy apps.
02
Press deliberate full chords; repeat the same chord before calling a key missing.
03
Test repeat and chatter with one key at a time so OS repeat is not confused with switch bounce.
Run one repeatable protocol.
- 01
Press the suspect key once at a time.
- 02
Repeat at least 20 deliberate presses.
- 03
Review per-key rapid reactivation flags and the event timeline.
Evidence the result should expose.
DIRECT / INFERREDPer-key flags
DIRECT / INFERREDReactivation interval
DIRECT / INFERREDDown/up timeline
Separate observed, review and inconclusive.
Repeat missing keys or rapid reactivations and compare the same chord in a plain text field or system tester.
Reserved shortcuts, OS repeat settings and browser focus can hide or reshape events without a keyboard fault.
Start with the likely path, then retest.
01
Switch contact bounce
02
Firmware debounce
03
OS key repeat