Skip to content

docs(spec): name the vendored input handler, not ghostty-web, in the key-binding and zoom paths - #54

Merged
jesse23 merged 1 commit into
mainfrom
docs/ghostty-web-wording
Oct 20, 2026
Merged

jesse23 merged 1 commit into
mainfrom
docs/ghostty-web-wording

Conversation

@jesse23

@jesse23 jesse23 commented Oct 20, 2026

Copy link
Copy Markdown
Owner

Wording only. After ADR 041 and ADR 047, webtty no longer depends on the npm ghostty-web package. Its terminal is the official libghostty-vt engine, with a renderer and input layer vendored from ghostty-web and heavily modified. Several spec passages still said "ghostty-web" handles keys, as if the npm package did the input.

  • docs/specs/client.md: the Keyboard Bindings and font-zoom passages and the Terminal view feature row.
  • docs/specs/key-bindings.md: the Description and Client implementation passages.

These passages now say "the terminal's input handler (vendored from ghostty-web, encoding keys with libghostty-vt's key encoder)" and name features/keyboard/key-dispatcher.ts. The README, the licence files and the passages describing the vendored layer itself are unchanged, because they were already accurate.

@jesse23
jesse23 merged commit 1c945ca into main Oct 20, 2026
3 checks passed
@jesse23
jesse23 deleted the docs/ghostty-web-wording branch October 20, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant