@cplieger/web-terminal-ui 5.6.0 → 5.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "5.6.0",
+  "version": "5.6.1",
   "type": "module",
   "description": "Reference touch-first browser UI for @cplieger/web-terminal-engine: a composable kernel + feature modules (tabs, activity monitor, mobile toolbar, context menu, IME, predictive echo, viewport handling) and CSS. One createTerminal() call.",
   "license": "MPL-2.0",
@@ -57,7 +57,7 @@
     "fast-check": "4.9.0",
     "happy-dom": "20.11.2",
     "html-validate": "11.6.2",
-    "knip": "6.32.1",
+    "knip": "6.32.2",
     "prettier": "3.9.6",
     "stylelint": "17.14.1",
     "stylelint-config-standard": "40.0.0",

package/src/dom-isolation-setup.ts

@@ -0,0 +1,32 @@
+// Per-test cleanup of DOM state that outlives a test file.
+//
+// Loaded via vitest's `setupFiles` alongside fc-strict-setup, because
+// `vitest.config.ts` deliberately sets `isolate: false`: test FILES share one
+// happy-dom instance inside a worker thread, which is what makes the suite fast
+// and also what lets one file's leftovers reach another's assertions.
+//
+// The document selection is the state that actually bites, for two compounding
+// reasons. Several suites end with a live selection on purpose (the kernel's
+// mouse-selection and type-to-focus suites assert that a gesture PRESERVED one,
+// and contextMenu's dismissal suite clicks a real Select All). And happy-dom does
+// not apply the selection fixup a real browser does, so a range whose nodes were
+// removed by `document.body.replaceChildren()` keeps reporting its old text:
+// measured rangeCount 1, isCollapsed false, and toString() unchanged after the
+// nodes were detached.
+//
+// Left alone, that reached `context-menu.test.ts`'s "omits Copy with nothing
+// selected" case, which found text to copy and failed. Order-dependently, so it
+// passed every local run and every PR check, then failed once on main where the
+// thread layout put the files in a different order. Clearing here rather than in
+// each suite keeps the guarantee independent of which files a worker happens to
+// pair up.
+import { beforeEach } from "vitest";
+
+beforeEach(() => {
+  // Node-environment files (the default; DOM files opt in per file) have no
+  // window, and nothing to clean.
+  if (typeof window === "undefined") {
+    return;
+  }
+  window.getSelection()?.removeAllRanges();
+});

package/src/features/tabs/index.ts

@@ -2561,6 +2561,20 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         if (activeId !== null) {
           return;
         }
+        // ...but only once the bootstrap has adopted its list. Before that the
+        // view is PARTIAL, and deterministically so: tabs subscribes to the status
+        // stream during setup, before resolveInitialSession issues its
+        // GET /api/sessions, so the SSE snapshot's one-event-per-session arrives
+        // first and this ran on a strip holding only whichever session the server
+        // sent first. Activating it both picked a tab on incomplete information and
+        // silently disabled the saved-tab restore: the bootstrap ladder's first act
+        // is to return early when activeId is already set, so localStorage was
+        // never read and every reload landed on the oldest tab. Boot activation
+        // belongs to that ladder alone, which is the only site with the whole list
+        // AND the saved id; this stays the runtime repair it was written to be.
+        if (!started) {
+          return;
+        }
         const first = tabList.find((t) => !isEndedStatus(statusOf(t))) ?? tabList[0];
         if (first) {
           switchTo(first.id);
@@ -4025,10 +4039,14 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         }
         // From here on, tabs added at runtime (create / adopt) animate in.
         started = true;
-        // The SSE snapshot may have raced this bootstrap and already activated
-        // a tab (ensureActive during the await above). The switch is then
-        // already in flight — return null; the kernel sees connectionInitiated
-        // and leaves the loading overlay to the normal ready path.
+        // Something already activated a tab while the list was in flight. The
+        // chrome mounts synchronously, so a user can tap a chip (or a delivered
+        // notification can be clicked) before this resolves, and an explicit
+        // gesture outranks the saved id — return null and leave that switch alone;
+        // the kernel sees connectionInitiated and leaves the loading overlay to
+        // the normal ready path. ensureActive is deliberately NOT one of these
+        // callers during boot (see its `started` gate): when it was, the SSE
+        // snapshot won this race on every load and the ladder below never ran.
         if (activeId !== null) {
           return null;
         }