Skip to content

CUD stops at bottom

Category: cursor · Baseline: core · Tags: ECMA-48 Standard, VT100 · Specification ↗

CUD (Cursor Down, CSI Pn B) should stop at the bottom margin of the scroll region, or the last row if no scroll region is set. Moving down with a count exceeding the remaining rows should clamp to the last row rather than scrolling or wrapping. Unlike a linefeed at the bottom margin, CUD never triggers scrolling — it simply stops.
How this is testedautomated
Position at row 0, send \x1b[999B (CUD with count 999), verify cursor stopped at the last row.

The same probe runs against headless backends (via Termless) and real terminal apps (via a daemon launched in each terminal). This lets us distinguish parser correctness from rendering correctness.

Analysis2026-04-06

Supported by all 12 tested terminals — universal adoption. Part of the Core TUI baseline.

Supported by 13 of 14 backends (93%)

Terminal Applications

TerminalVersionSupportNotes
iTerm23.6.9✓ yescursor at row 25
Ghostty1.3.1✓ yescursor at row 119
VS Code✓ yes
Warp✓ yes
Cursor✓ yes
Terminal.app✓ yes

Headless Backends

Parser correctness only — a means the parser accepts the sequence.

BackendVersionSupportNotes
Alacritty0.26.0✓ yes
Kitty0.40.0✓ yes
vt100.js0.2.1✓ yes
vterm0.2.0✓ yes
WezTerm0.1.0-fork.5✓ yes
xterm.js5.5.0✓ yes