Only one application duplicates
Check that application's shortcuts, extensions, text expansion, accessibility options, and input handling. A keyboard-level cause is less strongly supported.
Double-input troubleshooting
If one press sometimes produces two characters, test the suspect key for unusually close duplicate input patterns before assuming the keyboard is defective.
Quick test
Press the key you want to check The first detected key becomes the selected key for this sample.
Press the selected key normally 20–30 times without holding it down.
Detected presses will appear here.
Outcome map
Reproduce the same single-key symptom in controlled places. The pattern across applications and devices is more informative than one result by itself.
Check that application's shortcuts, extensions, text expansion, accessibility options, and input handling. A keyboard-level cause is less strongly supported.
Repeat a normal sample in another browser. The symptom may be intermittent or may depend on character processing that this physical-position test does not reproduce.
Repeat the sample without deliberately tapping fast, then compare another browser. One browser observation is a reason to investigate, not a hardware verdict.
That may be normal operating-system key repeat or an application's hold behavior. The chatter measurement excludes events marked repeat.
Review software, extensions, remapping, accessibility settings, and connection behavior on the original computer before considering keyboard service.
A keyboard-level source becomes more plausible when normal single presses duplicate across applications and computers, but browser evidence still cannot identify the component.
Define the symptom
Use one brief, ordinary press. If the application adds a second character after the key has been released, record which key and application were involved. A stream of characters while the key remains down is a different behavior and may be normal repeat.
The embedded test compares one physical KeyboardEvent.code. A text editor also shows the character produced by the active layout and application. Using both views helps separate event detection from text processing.
Use controlled comparisons
Begin in the application where the symptom occurs, then try a simple text field, this browser test, and another browser. If practical, move the same keyboard to another computer without changing several settings at once.
Write down whether the problem follows one key, one application, one computer, or the keyboard itself. That pattern determines whether software configuration, connection behavior, or the keyboard path deserves the next check.
Symptom-isolation path
Keep the same suspect key and use normal single presses throughout.
Reproduce the symptom. Confirm that one fully released press produces two characters rather than a held stream.
Compare a simple application. Test the same key in a basic text field to see whether the behavior belongs to one program.
Run the event sample. Use normal presses in the embedded chatter test; do not race the timing threshold.
Change browser. A different result can point toward extensions, browser scheduling, or page-specific handling.
Change computer if practical. If the symptom follows an external keyboard, use the manufacturer's documented support or service process.
Privacy and limitations
Key codes, timing intervals, and the recent sample remain in temporary browser memory and clear on reset or reload. Nothing here confirms defective hardware. For a longer dedicated sample, use the full Keyboard Chatter Test.