Focused Keyboard Event Tester

How to use Focused Keyboard Event Tester

Check which keyboard event fields this browser exposes when you intentionally focus a dedicated empty test area. Logical key and physical code remain separate source observations, which helps examine layouts and repeats without pretending that a page can certify the keyboard hardware.

1. Run, then select Arm keyboard area and keep its empty test surface focused.
2. Press the keys you want to inspect; Tab leaves normally and Escape returns to the controls.
3. Review the bounded local log, explicitly download if needed, or clear/reset the session.

Good to know

• Only focused, explicitly armed area keydown/keyup events are observed. No document/window keyboard handler, password input listener, global shortcut interception or permission request is used.
• The latest 100 bounded records are retained, with a 10,000-observation session cap. Each text field is at most 64 Unicode scalars; unsupported oversized/invalid observations are refused.
• Tab and Escape are never prevented. Blur disarms capture. Browser/OS shortcuts may never reach the page; key/code/repeat/modifiers can vary by layout, accessibility software and input method. No hardware, rollover or security certification is implied.
• The log can reveal what you deliberately type in the area. Avoid secrets. Output updates are coalesced; no storage or network transmission is made, and disposal removes all owned handlers.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.