Compact layout diagnostic

Laptop Keyboard Test

Test a focused laptop-style layout with no dedicated numpad by default, or switch to a general laptop-with-numpad view when that better matches your keyboard.

Key state remains in temporary browser memory.

Compact layout test

Press each key on your laptop

Choose the closest general layout

Manufacturer layouts vary. Changing this option starts a clean test for the selected layout.

Keys tested0 / 76

Last key—

Currently pressed0

Swipe sideways if the compact layout is wider than your screen.

~`
!1
@2
#3
$4
%5
^6
&7
*8
(9
)0
_-
+=
Backspace

Tab
Q
W
E
R
T
Y
U
I
O
P
{[
}]
|\

Caps Lock
A
S
D
F
G
H
J
K
L
:;
"'
Enter

Shift
Z
X
C
V
B
N
M
<,
>.
?/
Shift

Ctrl
OS
Alt
Space
Alt
Ctrl

Untested Pressed now Tested

Fn is intentionally not represented as a detectable browser key.

Built-in keyboard workflow

Test the laptop path separately

Choose the closest general layout, not a claimed model match.
Test the built-in keyboard first, including arrows and observable modifiers.
Repeat the same physical function in another application where practical.
Connect an external USB or Bluetooth keyboard and compare the equivalent key.
Record whether the symptom follows the key function, the application, or only the built-in keyboard.

Compact layout differences

Laptops may combine navigation keys, omit right-side modifiers, shrink arrows, or move Delete and power controls. This visual is representative, not a manufacturer-specific diagram.

Embedded and dedicated numpads

A compact laptop may expose number-pad behavior through an Fn layer, while a larger laptop may send distinct Numpad1-style codes. Use the optional view only for a dedicated physical keypad. For deeper checks, use the Numpad Test.

Fn and Fn Lock limitations

Fn is often handled by keyboard firmware and may never create a browser event. Brightness, volume, keyboard backlight, airplane mode, and other Fn-layer controls can also be processed outside the page. This tool does not create a fake Fn result.

Manufacturer function behavior

Top-row defaults and Fn Lock behavior vary by laptop and may be controlled by firmware or manufacturer utilities. A browser cannot inspect that configuration. The Function Keys Test explains browser-sensitive F-key behavior.

What detection proves

A tested state means the browser received a matching physical KeyboardEvent.code. An untested state does not prove hardware failure; layout, shortcuts, drivers, firmware, focus, and accessibility settings can affect events.

Private by design

The test keeps pressed, tested, and last-key state in this page's memory. It does not save raw key events, timings, or typed content, and it does not send them to a server.

Laptop outcome matrix

Compare the built-in and external keyboard paths

Use the same intended key function in each comparison. The pattern can narrow the investigation without identifying a physical cause.

Built-in key fails; external equivalent works

The symptom is more localized to the built-in keyboard path, its firmware, layout, driver, or physical assembly. A browser event cannot distinguish those sources.

Both fail in one application

Check that application's binding, shortcut handling, focus, and accessibility settings before assuming either keyboard is faulty.

Both fail across browser and applications

Review the active layout, operating-system input settings, remapping, and the exact function being tested. Reserved or firmware-handled actions may not expose browser events.

Fn-layer action works but no key appears here

The laptop may process that action in firmware, an embedded controller, a driver, or the operating system. Absence from the page is not a failed Fn-layer key.

Dedicated numpad works; embedded layer does not

An embedded Fn-layer number does not necessarily report a Numpad physical code. Use the dedicated Numpad Test only when the laptop exposes separate keypad positions.

Example interpretations

Examples from a laptop comparison

These examples explain possible outcomes. They are not results from your current session.

Both keyboard paths observed

Observed: The laptop key and a connected keyboard equivalent each produce the expected physical-position event.
May mean: This browser received that position from both input devices.
Does not prove: That firmware-layer actions or every program binding also work.
Next step: Continue across the laptop rows or reproduce the original symptom in its program.

Difference limited to the laptop

Observed: The laptop position remains unobserved while a connected keyboard supplies the equivalent code.
May mean: The contrast narrows attention toward the integrated keyboard path.
Does not prove: A failed switch, internal cable, driver, firmware component, or other specific cause.
Next step: Try a second program and follow the laptop maker's documented diagnostics.

Firmware-layer action without a code

Observed: Brightness, media, Fn, or an embedded keypad action occurs without a standard page event.
May mean: Firmware, an embedded controller, or the operating system may have handled the action.
Does not prove: That the top-row or function-layer control failed.
Next step: Check the manufacturer's Fn/Fn Lock documentation and verify the intended system action.