@cplieger/web-terminal-ui 6.1.4 → 7.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "6.1.4",
+  "version": "7.0.0",
   "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",
@@ -40,7 +40,7 @@
     "verify": "bash scripts/verify.sh"
   },
   "peerDependencies": {
-    "@cplieger/web-terminal-engine": "^3.10.0 || ^4.0.0 || ^5.0.0"
+    "@cplieger/web-terminal-engine": "^5.0.3"
   },
   "overrides": {
     "qs": "^6.15.2"
@@ -52,7 +52,7 @@
     "@stryker-mutator/vitest-runner": "10.0.0",
     "@types/node": "26.2.0",
     "@typescript/native": "npm:typescript@7.0.2",
-    "@vitest/coverage-v8": "4.1.10",
+    "@vitest/coverage-v8": "4.1.11",
     "eslint": "10.8.1",
     "fast-check": "4.9.0",
     "happy-dom": "20.11.2",
@@ -63,7 +63,7 @@
     "stylelint-config-standard": "40.0.0",
     "typescript": "npm:@typescript/typescript6@6.0.2",
     "typescript-eslint": "8.67.0",
-    "vitest": "4.1.10"
+    "vitest": "4.1.11"
   },
   "publishConfig": {
     "access": "public"

package/src/features/scroll-to-bottom.ts

@@ -47,7 +47,16 @@ export function scrollToBottom(): TerminalFeature {
           ctx.scroll.scrollToBottom();
           return;
         }
-        surface.scrollTo({ top: surface.scrollHeight, behavior: "smooth" });
+        // Target the MAXIMUM offset, not scrollHeight. An over-scroll target is
+        // one clientHeight past the end and needs the container to clamp it,
+        // which is the assumption the engine's own bottom writes stopped making:
+        // clamping an offset the content shrank out from under is an
+        // implementation behaviour and WebKit does not do it. The line above
+        // already computes the maximum, so this is the same arithmetic said once.
+        surface.scrollTo({
+          top: surface.scrollHeight - surface.clientHeight,
+          behavior: "smooth",
+        });
       };
 
       // pointerdown (like the toolbar keys) so touch devices get the jump on the

package/src/kernel/kernel.ts

@@ -601,7 +601,13 @@ function buildTerminal(
 
   connection.init({
     computeSize: render.computeSize,
-    getHaveThrough: render.getHighestIndex,
+    // getHaveThrough is deliberately NOT supplied. The engine defaults it to its
+    // own renderer (engine >= 5.0.3), which is the only party that knows which
+    // store is currently bound and which of its rows the server has confirmed.
+    // Supplying it from here is what claimed rows the application had merely
+    // DRAWN — `render.getHighestIndex` is the window's bottom row — and left a
+    // frozen copy of the composer parked in scrollback on almost every reattach.
+    // An explicit member wins over the default, so re-adding one reopens that.
     // --- Demand-paged scrollback (engine docs/paged-scrollback.md §4-5) ---
     // The transport is store-blind and viewport-blind by design, so every one of
     // these forwards a decision only the renderer can make. Without them the
@@ -811,7 +817,12 @@ function buildTerminal(
       case "scroll-down": {
         ev.preventDefault();
         const h = termWrap.clientHeight;
-        termWrap.scrollTop = Math.min(termWrap.scrollHeight, termWrap.scrollTop + h);
+        // The ceiling is the maximum offset, not scrollHeight: the latter is one
+        // clientHeight past the end, so a page-down near the bottom handed the
+        // container an out-of-range offset and relied on it to clamp. Same
+        // reasoning as the engine's bottom writes.
+        const max = Math.max(0, termWrap.scrollHeight - h);
+        termWrap.scrollTop = Math.min(max, termWrap.scrollTop + h);
         return true;
       }
       case "ignore":