collin/browser-terminal-extension · a71dc952

Drop stale autorepeat bursts flushed into the terminal under CPU load

Collin Richards · 2026-08-17 22:21 UTC · a71dc9528f5d70932d60b380d72f96bed25332d9 · parent ea0845f8 · browse files

modifiedextension/sidebar.js+902 −134

⋯ 23 unchanged lines
24	24
25	25		/** @param {string} id @returns {HTMLInputElement} */
26	26		const $input = (id) => /** @type {HTMLInputElement} */ ($(id));
	27	+	/** @param {string} id @returns {HTMLTextAreaElement} */
	28	+	const $area = (id) => /** @type {HTMLTextAreaElement} */ ($(id));
27	29		/** @param {string} id @returns {HTMLSelectElement} */
28	30		const $select = (id) => /** @type {HTMLSelectElement} */ ($(id));
29	31		/** @param {string} id @returns {HTMLButtonElement} */
⋯ 106 unchanged lines
136	138		// The name field comes with it: "+" holds the menu that makes a session
137	139		// now, and the field it opens has to be in a row that is on screen.
138	140		row.append($("tab-new"), $("session-name"));
139		-	// Picker and jump stay the pair they are in the nested layout, and follow
140		-	// jump into the row below — controls that act on a pane rather than on the
141		-	// tabs, at the start of the row you type into. Enter is not in either row:
142		-	// it lives under the mic, in the corner beside every row, and so never
143		-	// moves with the layout.
144		-	$("omni-strip").prepend($("pick"), $("jump"));
	141	+	// Picker and jump both follow the tabs into the row below — controls that
	142	+	// act on a pane rather than on the tabs — but they take opposite ends of
	143	+	// it: the picker leads, and jump sits past the box, at the end of the row
	144	+	// you type into, where what it does is leave for somewhere else. Enter is
	145	+	// not in either row: it lives under the mic, in the corner beside every
	146	+	// row, and so never moves with the layout.
	147	+	$("omni-strip").prepend($("pick"));
	148	+	$("omni-strip").append($("jump"));
145	149		$("omni-strip").hidden = false;
146	150		// The session row is gone, so what it was showing has to go with it: a
147	151		// stale session tab left in a hidden strip still answers `querySelector`
⋯ 128 unchanged lines
276	280		term.open($("term"));
277	281		fit.fit();
278	282
	283	+	// Autorepeat under load. When the browser process is starved, the key's
	284	+	// release sits in the queue behind it while the OS keeps generating repeats
	285	+	// for a key it still believes is held; when the process catches up, the whole
	286	+	// backlog is flushed into the pty at once and a single tap comes out as a row
	287	+	// of characters. Nothing here can stop the OS repeating, but the burst is
	288	+	// easy to tell from a real hold: genuine autorepeat arrives ~30ms apart with