@cplieger/web-terminal-ui 4.2.0 → 4.3.1

package/README.md

@@ -137,14 +137,14 @@ are importable from `…/features/<name>` (`clipboard`, `context-menu`,
 
 ### Options
 
-| Option      | Default                    | Purpose                                                                                                                                                                                                                                        |
-| ----------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `features`  | _(none — bare kernel)_     | The feature list. Omitted or empty builds only the terminal (no chrome). Use a preset from `./presets` or a hand-picked array.                                                                                                                 |
-| `layout`    | `"viewport"`               | How the terminal claims space. `"viewport"`: the root becomes a fixed full-viewport box (the full-page product). `"container"`: the root fills your container element, which becomes the styling and positioning boundary (the embedded case). |
-| `wsPath`    | `"/ws"`                    | WebSocket endpoint path the engine connects to.                                                                                                                                                                                                |
-| `fontReady` | `'14px "MonaspiceNe NFM"'` | CSS font shorthand awaited before the first resize, so the server is sized against the real web font's cell metrics rather than a fallback.                                                                                                    |
-| `loading`   | _(none)_                   | A pre-JS loading overlay element (kept in your served HTML so it paints before this module loads); it is faded out and removed once the first frame renders.                                                                                   |
-| `theme`     | _(none)_                   | Theme overrides (CSS custom properties on the terminal root): `--accent`, `--tab-bg`, `--tab-hover-bg`, `--tab-active-bg`, `--tab-active-fg`, `--tab-active-border`. The library ships neutral defaults.                                       |
+| Option      | Default                    | Purpose                                                                                                                                                                                                                                                                                                                                                  |
+| ----------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `features`  | _(none — bare kernel)_     | The feature list. Omitted or empty builds only the terminal (no chrome). Use a preset from `./presets` or a hand-picked array.                                                                                                                                                                                                                           |
+| `layout`    | `"viewport"`               | How the terminal claims space. `"viewport"`: the root becomes a fixed full-viewport box (the full-page product). `"container"`: the root fills your container element, which becomes the styling and positioning boundary (the embedded case).                                                                                                           |
+| `wsPath`    | `"/ws"`                    | WebSocket endpoint path the engine connects to.                                                                                                                                                                                                                                                                                                          |
+| `fontReady` | `'14px "MonaspiceNe NFM"'` | CSS font shorthand awaited before the first resize, so the server is sized against the real web font's cell metrics rather than a fallback.                                                                                                                                                                                                              |
+| `loading`   | _(none)_                   | A pre-JS loading overlay element (kept in your served HTML so it paints before this module loads); it is faded out and removed once the first frame renders.                                                                                                                                                                                             |
+| `theme`     | _(none)_                   | Theme overrides (CSS custom properties on the terminal root): `--accent`, `--tab-bg`, `--tab-hover-bg`, `--tab-active-bg`, `--tab-active-fg`, `--tab-active-border`, plus the activity-dot palette `--status-working`, `--status-done`, `--status-input` (the working and input rings derive from their own tokens). The library ships neutral defaults. |
 
 `createTerminal()` returns a handle: `focus()` re-focuses the terminal input
 (and opens the soft keyboard on touch); `send(bytes)` sends bytes to the active

package/css/00-tokens.css

@@ -44,6 +44,13 @@
     var(--text) 25%
   ); /* subtle edge: the fill lightened + slightly desaturated, matching the inactive chip's faint border rather than a vivid accent outline */
 
+  /* Status-dot palette (the activity vocabulary painted in 30-tabs.css; the
+     switcher notification dot reuses the same rules). The working and input
+     rings each derive from their own token in 30-tabs.css, so one override
+     recolors dot + ring together. */
+  --status-working: #d9f99d; /* agent working (pulses): pale lime */
+  --status-done: #22c55e; /* turn finished: solid green */
+  --status-input: #fb923c; /* action required: solid orange + ring */
   --radius: 0.75rem;
   --radius-inner: 0.5rem;
   /* Small square icon buttons (e.g. the 24px tab-close x): at that size the

package/css/30-tabs.css

@@ -13,10 +13,10 @@
 
 :where(.wt-root) .wt-tab-bar {
   /* Absolute against .wt-root, like all chrome (identical geometry in
-     wt-viewport mode; see 01-scope.css). The bar itself never scrolls: the
-     tabs + "+" scroll inside .wt-tab-scroll (below), so the keyboard button —
-     the bar's last flex item, outside the scroller — stays pinned at the right
-     edge however many tabs are open. */
+     wt-viewport mode; see 01-scope.css). The bar itself never scrolls: only
+     the tabs scroll, inside .wt-tab-scroll (below); the "+" and the keyboard
+     button are fixed bar items after it, so both stay visible at the bar's
+     right edge however many tabs are open. */
   position: absolute;
   bottom: var(--safe-bottom);
   left: 0;
@@ -32,17 +32,22 @@
   z-index: 15;
 }
 
-/* The scrolling tab list inside the bar: the tabs plus the "+", which floats
-   right of the last tab and scrolls with the list. Horizontal scrolling lives
-   HERE, not on the bar, so the strip-end keyboard button never scrolls away.
-   flex: 1 + min-width: 0 make it shrink to leave room for the keyboard button
-   when that is shown (a wide touchscreen) and stretch to the full bar width
-   when it is hidden (a fine-pointer desktop), so the tabs reclaim the space. */
+/* The scrolling tab list inside the bar: the tabs and nothing else — the "+"
+   and the keyboard button are fixed bar siblings after it. Horizontal
+   scrolling lives HERE, not on the bar, so neither control ever scrolls away.
+   flex: 0 1 auto + min-width: 0 shrink-WRAP the list: while the tabs fit, the
+   scroller is exactly as wide as its content and the "+" trails the last tab
+   across the bar gap (visually identical to living in the list); once the
+   tabs overflow, the scroller caps at the space the fixed controls leave and
+   the "+" reads as pinned at the bar's right edge (with the keyboard button,
+   when shown on a wide touchscreen, anchored to its right). The tabs feature
+   also maps a vertical wheel over the bar to scrollLeft here — the strip has
+   no vertical scroll to spend it on. */
 :where(.wt-root) .wt-tab-scroll {
   display: flex;
   align-items: center;
   gap: var(--sp-1);
-  flex: 1 1 auto;
+  flex: 0 1 auto;
   min-width: 0;
   overflow-x: auto;
   /* A wheel/trackpad/touch scroll that runs out of tabs must not chain into
@@ -164,9 +169,12 @@
   }
 }
 
-/* The add-tab (+) button: its hover box matches an active tab's fill and
-   stretches to the strip height; the 2px strip gap (not a custom margin) spaces
-   it from the last tab. Its glyph is an inline SVG. */
+/* The add-tab (+) button: a fixed bar item OUTSIDE the tab scroller (it never
+   scrolls away with an overflowing list; the shrink-wrapped scroller keeps it
+   visually trailing the last tab while the tabs fit — see .wt-tab-scroll). Its
+   hover box matches an active tab's fill and stretches to the strip height;
+   the bar gap (not a custom margin) spaces it from the list. Its glyph is an
+   inline SVG. */
 :where(.wt-root) .wt-tab-new {
   display: inline-flex;
   align-items: center;
@@ -226,8 +234,10 @@
    tab scroller: pinned at the bar's right edge in the same column as the
    scroll-to-bottom button floating above it (both 44px boxes whose right edge
    sits --sp-2 from the root's right edge), where an overflowing tab list can
-   never push or scroll it away; the "+" stays with the tabs inside the
-   scroller. Hidden on a fine-pointer desktop (a real keyboard is present; the
+   never push or scroll it away — margin-left: auto (below) keeps it there
+   whatever the tab count. The "+" is likewise a fixed bar item outside the
+   scroller, but it TRAILS the tab list (the auto margin sits between them)
+   and packs up against the kb only when the strip overflows. Hidden on a fine-pointer desktop (a real keyboard is present; the
    scroller then stretches to the full bar width) and until a keyboardToggle
    feature is wired ([hidden]); shown only on a coarse pointer at strip widths
    (the .wt-narrow complement below; the breakpoint itself is the kernel's,
@@ -235,6 +245,11 @@
 :where(.wt-root) .wt-tab-kb {
   display: none;
   flex: none;
+  /* Pin at the bar's FAR right edge always: the auto margin absorbs whatever
+     width the shrink-wrapped scroller + "+" leave free, so the kb button's
+     position is independent of the tab count (the "+" trails the tab list and
+     only packs up against the kb once the strip overflows). */
+  margin-left: auto;
 }
 
 /* Grid open: filled so the toggled state reads at a glance (mirrors the
@@ -376,33 +391,42 @@
   border: 1.5px solid color-mix(in oklch, var(--text) 45%, transparent);
 }
 
-/* Agent working: solid pulsing pale lime. Its high lightness keeps it clear on
-   every tab state, while its yellow-green hue complements the Kiro purple active
-   tab. Motion is the primary non-hue cue. Server-side this is driven by the OSC
-   9;4 progress signal, so it tracks agent activity, not the user typing at the
-   prompt. */
+/* Agent working: solid pulsing dot (--status-working; pale lime by default —
+   its high lightness keeps it clear on every tab state) wearing the same 2px
+   ring as input, so the two agent-turn states share one silhouette: a live
+   turn pulses (dot + ring together), a turn blocked on the user is that same
+   silhouette frozen and recolored (input, below). Motion separates working
+   from input; the ring separates both from done's bare disc. Server-side this
+   is driven by the OSC 9;4 progress signal, so it tracks agent activity, not
+   the user typing at the prompt. */
 :where(.wt-root) .wt-status-dot[data-status="working"] {
-  background: #d9f99d;
-  border-color: #d9f99d;
+  background: var(--status-working);
+  border-color: var(--status-working);
+  box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
   animation: wt-pulse 1.2s ease-in-out infinite;
 }
 
-/* Agent done / ready: solid saturated green, matching Kiro IDE's "Ready"
-   (#22c55e), no motion. Keeping it darker and more saturated than working's
-   pale lime makes the two states distinct by lightness as well as motion. */
+/* Agent done / ready: solid disc (--status-done), no motion. The default green
+   matches Kiro IDE's "Ready" (#22c55e), darker and more saturated than
+   working's default pale lime so the two states differ by lightness as well as
+   motion. */
 :where(.wt-root) .wt-status-dot[data-status="done"] {
-  background: #22c55e;
-  border-color: #22c55e;
-}
-
-/* User action required (permission / approval): solid orange (#fb923c), shifted
-   away from the old amber so it is clearly separated from both pale-lime working
-   and green done, plus a matching ring so it reads as "needs you" via shape as
-   well as hue. It persists until you act on or switch into the tab. */
+  background: var(--status-done);
+  border-color: var(--status-done);
+}
+
+/* User action required (permission / approval): working's exact silhouette —
+   solid dot + 2px ring — frozen and recolored (--status-input; the default
+   orange is shifted away from the old amber so it separates from both
+   default-lime working and green done). The stillness is the message: the
+   agent's turn is mid-flight but blocked on you. The ring keeps it distinct
+   from done's bare disc without leaning on hue; it derives from the same token
+   at 40% alpha, so a theme override recolors dot + ring together. It persists
+   until you act on or switch into the tab. */
 :where(.wt-root) .wt-status-dot[data-status="input"] {
-  background: #fb923c;
-  border-color: #fb923c;
-  box-shadow: 0 0 0 2px rgb(251 146 60 / 40%);
+  background: var(--status-input);
+  border-color: var(--status-input);
+  box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-input) 40%, transparent);
 }
 
 /* Exited: a dim hollow dot, static; distinct from idle by its lower opacity. */
@@ -417,15 +441,18 @@
   100% {
     /* Pin the animated layer's paint as well as its opacity. When working begins
        in the same frame that input/done ends, an opacity-only animation can
-       pulse the previously rasterized orange/green dot. */
-    background-color: #d9f99d;
-    border-color: #d9f99d;
+       pulse the previously rasterized input/done paint (the input ring
+       included, hence the box-shadow pin). */
+    background-color: var(--status-working);
+    border-color: var(--status-working);
+    box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
     opacity: 1;
   }
 
   50% {
-    background-color: #d9f99d;
-    border-color: #d9f99d;
+    background-color: var(--status-working);
+    border-color: var(--status-working);
+    box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
     opacity: 0.4;
   }
 }
@@ -434,10 +461,13 @@
 @media (prefers-reduced-motion: reduce) {
   :where(.wt-root) .wt-status-dot[data-status="working"] {
     animation: none;
-    /* The pulse is working's ONLY non-hue cue; with motion removed,
-       add a static shape cue (an inner hole -> a ring) so working differs
-       from done (a solid green disc) by shape, not hue alone (WCAG 1.4.1). */
-    box-shadow: inset 0 0 0 2px var(--bg);
+    /* The pulse is what separates working from input's frozen silhouette; with
+       motion removed, punch an inner hole (dot -> donut) so working differs
+       from input (solid ringed disc) and done (bare disc) by shape, not hue
+       alone (WCAG 1.4.1). The outer ring stays. */
+    box-shadow:
+      inset 0 0 0 2px var(--bg),
+      0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
   }
 }
 

package/css/31-switcher.css

@@ -280,10 +280,11 @@
 }
 
 /* Latest-wins background-tab notification dot on the switch button — the moved
-   attention cue. Amber = a background terminal needs input, green = a background
-   turn finished. Reuses the exact .wt-status-dot colours (30-tabs.css) so it
-   matches the per-tab dots. Hidden until the tabs feature sets data-status;
-   cleared when the list opens (expandSwitcher). */
+   attention cue: the input colour when a background terminal needs input, the
+   done colour when a background turn finished. Reuses the exact .wt-status-dot
+   rules (30-tabs.css, --status-* tokens) so it matches the per-tab dots. Hidden
+   until the tabs feature sets data-status; cleared when the list opens
+   (expandSwitcher). */
 :where(.wt-root) .wt-switcher-switch-dot {
   position: absolute;
   top: 6px;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "4.2.0",
+  "version": "4.3.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": "GPL-3.0-or-later",

package/src/features/tabs/index.ts

@@ -225,17 +225,20 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
 
       // --- Desktop tab strip (top-bar region) ---
       // Two layers: the bar itself never scrolls; an inner scroller
-      // (.wt-tab-scroll, the tablist) holds the tabs plus the "+", which floats
-      // right of the tab list and scrolls WITH it when many tabs overflow. The
-      // keyboard button sits OUTSIDE the scroller as the bar's last flex item,
-      // pinned at the bar's right edge in the scroll-to-bottom button's column
-      // (an overflowing tab list can never push or scroll it away). On a fine
-      // pointer it is display:none (CSS), and the scroller stretches to the
-      // full bar width so the tabs reclaim that space. Both controls are built
-      // + wired by the same shared factories as the mobile switcher's; the kb
-      // button is CSS-gated to a wide touchscreen and un-hidden below only when
-      // a keyboardToggle is wired. addTabChrome inserts each tab before newBtn,
-      // keeping the scroller [tabs… +].
+      // (.wt-tab-scroll, the tablist) holds ONLY the tabs. The "+" and the
+      // keyboard button sit OUTSIDE the scroller as fixed bar items in the
+      // order [scroller | + | kb], so an overflowing tab list can never push
+      // or scroll either control away. The scroller shrink-wraps its content
+      // (CSS flex: 0 1 auto), so while the tabs fit the "+" trails the last
+      // tab exactly as if it were in the list, while the kb button (a wide
+      // touchscreen; hidden on a fine pointer) stays pinned at the bar's FAR
+      // right edge via margin-left: auto whatever the tab count. Once the
+      // tabs overflow, the scroller caps at the remaining bar width and the
+      // "+" packs right, up against the kb. Both controls are built + wired
+      // by the same shared factories as the mobile switcher's; the kb button
+      // is CSS-gated to a wide touchscreen and un-hidden below only when a
+      // keyboardToggle is wired. addTabChrome appends each tab to the
+      // scroller's end.
       const slot = ctx.region("top-bar", "tabs");
       const bar = document.createElement("div");
       bar.className = "wt-tab-bar";
@@ -245,9 +248,38 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
       scroller.setAttribute("role", "tablist");
       bar.appendChild(scroller);
       const newBtn = makeNewButton("wt-tab-new");
-      scroller.appendChild(newBtn);
+      bar.appendChild(newBtn);
       const deskKb = makeKbButton("wt-tab-kb wt-btn");
       bar.appendChild(deskKb);
+      // A vertical mouse wheel anywhere over the strip scrolls the tab list
+      // horizontally — the strip has no vertical dimension to spend the delta
+      // on, and this is the affordance browser tab bars train. Bound on the
+      // BAR so the empty strip area and the fixed controls translate too.
+      // Horizontal-dominant deltas (a trackpad pan) keep native handling, and
+      // a wheel over a non-overflowing strip falls through untouched. The
+      // listener is non-passive because a translated tick must preventDefault
+      // so an embedding page (wt-container mode) does not also scroll.
+      bar.addEventListener(
+        "wheel",
+        (e) => {
+          if (Math.abs(e.deltaY) <= Math.abs(e.deltaX)) {
+            return; // horizontal-dominant: native scroll already handles it
+          }
+          if (scroller.scrollWidth <= scroller.clientWidth) {
+            return; // nothing to scroll: let the page have the wheel
+          }
+          e.preventDefault();
+          // deltaMode: 0 = pixels, 1 = lines (Firefox wheel), 2 = pages.
+          const step =
+            e.deltaMode === 1
+              ? e.deltaY * 32
+              : e.deltaMode === 2
+                ? e.deltaY * scroller.clientWidth
+                : e.deltaY;
+          scroller.scrollLeft += step;
+        },
+        { passive: false },
+      );
 
       // Pull the terminal surface up off the docked BOTTOM strip on desktop so
       // the bar does not overlap the last rows. The surface is absolute
@@ -515,13 +547,27 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         ctx.surface().querySelector<HTMLElement>(".term-input")?.focus({ preventScroll: true });
       }
 
-      // paintActive updates the desktop strip's active state.
+      // paintActive updates the desktop strip's active state. When the ACTIVE
+      // TAB CHANGES (tracked via lastRevealedActive — not on every chrome
+      // sync, so a user browsing a scrolled strip is never yanked back by an
+      // unrelated repaint), the newly active chip is brought into view in the
+      // overflowed scroller; inline: "nearest" is a no-op when it is already
+      // visible. The typeof guard covers happy-dom, which lacks
+      // scrollIntoView.
+      let lastRevealedActive = "";
       function paintActive(): void {
         for (const t of tabList) {
           const on = t.id === activeId;
           t.el.classList.toggle("wt-tab-active", on);
           t.aria.setSelected(on);
         }
+        if (activeId && activeId !== lastRevealedActive) {
+          lastRevealedActive = activeId;
+          const active = tabList.find((t) => t.id === activeId);
+          if (active && typeof active.el.scrollIntoView === "function") {
+            active.el.scrollIntoView({ block: "nearest", inline: "nearest" });
+          }
+        }
       }
 
       // syncMobile updates the bottom bar: active label + dot, and the aggregate
@@ -868,9 +914,9 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         }
         paintStatusDot(dot, info.status, info.reportsActivity ?? false);
         const aria = tablist.registerTab(el);
-        // Insert before the "+" so it stays the last item of the scrolling tab
-        // list (the keyboard button lives outside the scroller, at the bar end).
-        scroller.insertBefore(el, newBtn);
+        // Append to the scroller's end: the tab list is ALL the scroller holds
+        // (the "+" and keyboard button are fixed bar items outside it).
+        scroller.appendChild(el);
         // Runtime-added tabs animate in; initial tabs do not (see `started`).
         // The timer (not animationend) also clears the class on the hidden mobile
         // strip, where the animation never fires.
@@ -1183,8 +1229,8 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
       }
 
       // dragTargetBefore returns the first tab whose horizontal midpoint is past
-      // x (the element the dragged tab should sit before), or null to drop at the
-      // end (before the "+"). syncOrderFromDom rebuilds tabList to
+      // x (the element the dragged tab should sit before), or null to drop at
+      // the end of the tab list. syncOrderFromDom rebuilds tabList to
       // match the strip's DOM order after a drag, so position indicators, the
       // switcher, and close-to-the-right/left all follow the visible order.
       function dragTargetBefore(x: number): HTMLElement | null {
@@ -1211,8 +1257,8 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         }
       }
 
-      // moveTab shifts a tab one slot left or right in tabList and re-inserts
-      // every tab element in list order (before the "+") so the DOM matches.
+      // moveTab shifts a tab one slot left or right in tabList and re-appends
+      // every tab element in list order so the DOM matches.
       // It is the single-pointer / non-drag alternative to the drag-and-drop
       // reorder (WCAG 2.5.7), surfaced as Move left / Move right in the tab
       // context menu.
@@ -1228,7 +1274,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         }
         tabList.splice(to, 0, tab);
         for (const item of tabList) {
-          scroller.insertBefore(item.el, newBtn);
+          scroller.appendChild(item.el);
         }
         syncChrome();
         ctx.announce(`Moved ${tab.display} to position ${String(to + 1)}`);
@@ -1694,7 +1740,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         if (e.dataTransfer) {
           e.dataTransfer.dropEffect = "move";
         }
-        scroller.insertBefore(draggingEl, dragTargetBefore(e.clientX) ?? newBtn);
+        scroller.insertBefore(draggingEl, dragTargetBefore(e.clientX));
       });
       // Active-row close (x): closes the current tab (mirrors a listed row's x).
       // stopPropagation so it is not read as a tap/swipe on the row surface.