
If movement stops when you hold another action key, test that exact combination before buying a new keyboard. A device can recognize every key on its own and still fail to report a particular group pressed together. The useful question is whether your game's required combinations work on your setup.
Microsoft's anti-ghosting explanation notes that an anti-ghosting claim can refer to a subset of keys. That makes the actual layout worth checking. A label on the box is less specific than a test of the keys you need.Check a physical keyboard
Simultaneous key check
On a physical keyboard, focus the box, then hold your intended game keys together. Tab leaves the box. Browser and operating-system shortcuts may intercept some combinations. No keys are stored or sent.
Without JavaScript, test the same combination in the game’s control screen or the manufacturer’s diagnostic tool. On a touch-only device, this test cannot establish physical-keyboard rollover.
The widget reports keyboard events delivered to this page. It cannot see a key that the browser or operating system intercepts, and it cannot prove what a particular game receives. Use a failed result as a reason to investigate, then repeat the action inside the game.
Start with the real combination
List movement and action inputs that occur together. For a hypothetical platform game, that might be moving right while jumping and holding an action. Use your actual bindings; there is no universal set of keys that represents every arcade game.
Press each key alone, then pairs, then the complete combination. Keep the order consistent for the first test, then try another order. Record which keys appear and which disappear. Avoid system shortcuts, password fields or sensitive text while testing.
Separate hardware from mappings
If the browser receives the full combination but the game does not respond, inspect the game's bindings and input rules. Two actions may share a key, or the game may intentionally ignore an action in that state. Check its instructions before treating the result as hardware failure.
If a combination fails in several appropriate tests, try a different supported binding. Change one key, repeat the same sequence and record the result. A small remap may solve the practical problem without requiring a different device.
Check shared-keyboard play
When two people use one keyboard, test both players' common combinations together. Each person's controls may work separately while the combined set fails. Use a safe test area in the game so the players can coordinate the input without losing progress.
Choose a layout that everyone can reach comfortably and that the game allows. Do not assume that attaching another keyboard creates separate input identities; many games treat keyboard input as one shared source. Consult the game's local multiplayer instructions.
Understand the browser result
The widget displays physical key codes where available, which can differ from the character printed by a particular keyboard layout. The MDN keyboard documentation explains how key values depend on modifiers and layout. What you see here is a diagnostic label, not a test of typing accuracy.
Focus must remain inside the test box. Leaving it clears the displayed held keys, and Tab remains available to move away. If a key appears stuck after a missed release event, leave and refocus the box before starting another test.
Save the working bindings in your own notes and apply them through the game's normal settings. After a remap, test menus and gameplay separately so that an improvement in one action does not make another required action inaccessible.
For an older platform-game entry, see SuperCow archive entry.


