Geometry & Inset Inspector

Auditing what Chrome reports vs what the W3C spec requires

VirtualKeyboard API
Overlay: ON
Viewport: — × —

API Not Available

Requires Chrome or Edge on Android (94+).

JS: navigator.virtualKeyboard.boundingRect
A DOMRect — the keyboard's intersection with the layout viewport in client coordinates. For a docked keyboard: .y = vpH−kbH, .bottom = vpH, .x = 0, .width = vpW.
Property
Actual
Expected
OK?
.x
—
—
—
.y
—
—
—
.width
—
—
—
.height
—
—
—
.top
—
—
—
.right
—
—
—
.bottom
—
—
—
.left
—
—
—
CSS: env(keyboard-inset-*)
The spec defines these as insets from the viewport edge, like safe-area-inset-*. For a docked keyboard: inset-top = vpH−kbH, inset-bottom = 0, left/right = 0.
Inset
Actual
Expected
OK?
top
—
—
—
right
—
—
—
bottom
—
—
—
left
—
—
—
width
—
—
—
height
—
—
—
Event Log