From b6f15b30c62735634ada4156a3a1e967f00f9440 Mon Sep 17 00:00:00 2001 From: Codeman maintainer Date: Fri, 14 Aug 2026 00:56:01 +0200 Subject: [PATCH] docs: correct the rewrite-anchor comment now that refresh pulls full history Co-Authored-By: Claude Opus 5 (1M context) --- src/web/public/constants.js | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/web/public/constants.js b/src/web/public/constants.js index 5988eeb6..78886f2a 100644 --- a/src/web/public/constants.js +++ b/src/web/public/constants.js @@ -851,10 +851,11 @@ function computeHistoryTruncationNotice(state = {}) { /** * Where to land after a rewrite that REPLACES the whole buffer (#259). * - * The backpressure refresh clears and reloads the terminal from a fresh tail, - * so an absolute viewportY captured beforehand means nothing afterwards: the - * line it pointed at may not even exist. Distance from the BOTTOM is the anchor - * that survives a rewrite, so a reader stays roughly where they were reading. + * The backpressure refresh clears the terminal and reloads it from a freshly + * fetched capture, so an absolute viewportY captured beforehand means nothing + * afterwards: the line it pointed at may not even exist. Distance from the + * BOTTOM is the anchor that survives a rewrite, so a reader stays roughly + * where they were reading. * * Returns null when the user was following live output, which the caller reads * as "scroll to bottom" — the historical behavior, kept for that case.