Public Access
laurensandClaude Opus 5
1908189100
Selecting output and right-clicking it opened the WebView's own context menu with Copy on it, which is correct behaviour for a web page and wrong for a terminal. What a terminal's right button has meant since the Windows console got QuickEdit, and since PuTTY shipped, is this: with something selected it copies and drops the selection, with nothing selected it pastes. No menu, no second click. The gesture can only live in the page. The selection is drawn into a canvas the host never sees, and once a terminal has focus the host's window receives no input events at all — the same reason the Ctrl+plus chords are handled there. ◆ THE CLIPBOARD IS THE HOST'S IN BOTH DIRECTIONS, AND THE READING IS WHY. navigator.clipboard.readText() is gated behind the clipboard-read permission in every Chromium, and an embedded WebView with no PermissionRequested handler answers a permission request by putting a prompt on the screen. Trading a context menu for a permission dialog is not this change. So the page asks and the host answers, exactly as requestFontSizeStep does. Writing does not go the other way either, although navigator.clipboard.writeText would have worked from the page on Windows: a clipboard that is the host's in one direction and the page's in the other is two mechanisms to keep working across WebView2, WebKitGTK and Android's WebView. The host has owned a clipboard delegate since the keychain grew its COPY buttons, so each App.axaml.cs grows a ClipboardReader beside its ClipboardWriter and MainWindowViewModel takes it. Three opcodes: client ClipboardCopy and ClipboardPaste, server Clipboard. ◆ Clipboard IS NOT Paste, AND THE DIFFERENCE IS THE BRACKETING. Paste carries a snippet off the sidebar, and the page deliberately *types* a single-line one rather than bracketing it, because bash marks a bracketed paste as an active region and a snippet should read as though it had been typed. A clipboard paste is the case those markers are for — readline uses them to decide it has been pasted into — so Clipboard is always bracketed and never followed by an Enter. One opcode for both would have needed a flag meaning "which of the two kinds of paste is this", on a payload whose existing flag byte means something else. Both client frames are dispatched before the session lookup, which is what keeps the gesture working in a pane whose shell has just ended: squinting at the message a remote left behind is exactly when somebody copies the line. Dispatch was past MA0051's length once it grew a second such branch, so the frames no pump needs to see moved into Announce() and the font-size chord went with them. ◆ CAPTURED AND STOPPED, RATHER THAN MERELY PREVENTED. preventDefault alone suppresses the menu and still lets xterm's own contextmenu handler run, which moves its helper textarea under the pointer at z-index 1000 and leaves the selection sitting in it, selected. Both of those exist to serve the native menu. Taking the event in the capture phase on the pane and stopping it there is what keeps the gesture wholly the page's. rightClickSelectsWord is now false, which on macOS is a change of default rather than a restatement of it: xterm sets it true there alone, so a right-click would have selected the word under the pointer and copied that instead of pasting — wrong on one platform only, which is the worst way for it to be wrong. The renderer harness grows the pane it has been inviting since RendererReconnectionTests: a fake Terminal, the two addons, and a real UTF-8 codec, because both directions run through the page's own TextEncoder and TextDecoder and a Latin-1 stub would pass a test with an em dash in the selection. Its warning about declaring names terminal.js declares now covers the half that does not SyntaxError — a harness frame() was silently replaced by the page's frame() and failed six tests on a type error a long way from the cause. Manual checks 1.11 and 11.13 are what is left for a person: that a real contextmenu event reaches a capture listener, that no native menu is drawn once it is prevented, and that xterm's real paste() brackets. 11.13 also records what is unverified — whether Android's WebView delivers a pointer's secondary click as a contextmenu event at all. ClipboardReader is wired on that head regardless, because the alternative is a head where the paste half silently does nothing and nobody finds out; that head is not compiled here either, this machine having no android workload. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Vendored third-party assets
Committed rather than fetched at build time, so a clean clone builds with the .NET SDK alone — no node, no npm, no esbuild step. The trade-off is that upgrades are a manual re-download, which is exactly why the provenance is written down here.
All of the following are MIT licensed, the same licence as this repository.
| File | Package | Version | Source |
|---|---|---|---|
xterm.js |
@xterm/xterm |
6.0.0 | https://unpkg.com/@xterm/xterm@6.0.0/lib/xterm.js |
xterm.css |
@xterm/xterm |
6.0.0 | https://unpkg.com/@xterm/xterm@6.0.0/css/xterm.css |
addon-fit.js |
@xterm/addon-fit |
0.11.0 | https://unpkg.com/@xterm/addon-fit@0.11.0/lib/addon-fit.js |
addon-webgl.js |
@xterm/addon-webgl |
0.19.0 | https://unpkg.com/@xterm/addon-webgl@0.19.0/lib/addon-webgl.js |
Copyright (c) 2017 The xterm.js authors. See https://github.com/xtermjs/xterm.js for the full licence text.
These are the UMD builds, so they attach to globalThis: Terminal, FitAddon.FitAddon and
WebglAddon.WebglAddon. terminal.js depends on those exact names, so check them after any upgrade
— a bundle that switched to ES modules would load without error and leave Terminal undefined.
Upgrading
- Download the four files at the new versions and update the table above.
- Confirm the UMD global names are unchanged.
- Confirm the right-click still belongs to
terminal.js. Two things about xterm are load-bearing for it and neither is a global:rightClickSelectsWordhas to still be an option — the page sets it false, and an option xterm no longer knows is silently ignored — and xterm has to still register its own right-click handling oncontextmenu, whichhandleRightClickgets ahead of in the capture phase. A build that moved that tomousedown, as it already is on the Firefox path, would put xterm back in the gesture. - Run the terminal suite, then start the app and open a session:
RendererClipboardTestsruns the page's own logic against a stubbed terminal, so what is left for a person is everything about the real one —docs/manual-checks.md1.11 is that list.