fix(board): hold scroll across live re-renders + order project lanes by recency (ready-6ec) - #237
Merged
baron-3dl merged 1 commit intoAug 8, 2026
Conversation
…es by recency (ready-6ec) TWO things a reader hit while just looking at the board: 1. THE VIEW JUMPED ON SCROLL. Every live fold (setItems) and board-state reconcile (setBoards) does render()'s replaceChildren(), which empties #app — and the PAGE is the scroll container here (the shell grows with content, so nothing scrolls internally). Emptying it clamps the page scroll to 0, so a reader scrolled halfway down was yanked to the top again and again as the first-minute stream of updates arrived. Capture the page scroll (and the panes, in case the layout is ever made pane-scrolling) before the rebuild and restore it after; refocus with preventScroll so it cannot fight. Real-browser check: page scroll 700 -> 700 across a live fold. 2. PROJECT LANES WERE ORDERED BY GATE COUNT, so a project stale for a week floated to the top just because it carried gates (enterpriseaiframework). Gates now live in their own banner at the very top, surfaced regardless of lane order, so the lanes answer the question a scroller actually has: order by MOST-RECENT activity, ties broken by name for a total (stable) order. Full board suite 1007 passing; tsc clean; scroll-hold verified in a real browser. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
baron-3dl
deleted the
fix/board-scroll-stable-and-recency-order-ready-6ec
branch
August 8, 2026 22:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two things a reader hit while just looking at the board.
1. The view jumped on scroll
Every live fold (
setItems) / board reconcile (setBoards) doesrender()'sreplaceChildren(), emptying#app. The page is the scroll container here (the shell grows with content — nothing scrolls internally), and emptying it clamps page scroll to 0. So a reader scrolled halfway down was yanked to the top again and again as the first-minute stream of updates arrived.Capture the page scroll (and the panes, in case the layout is ever made pane-scrolling) before the rebuild, restore after; refocus with
preventScroll. Real-browser check: page scroll 700 → 700 across a live fold.2. Project lanes ordered by gate count
A project stale for a week floated to the top just because it carried gates (
enterpriseaiframework). Gates now live in their own banner at the top, surfaced regardless of lane order — so lanes now order by most-recent activity, ties broken by name (total, stable order).Verified
Board suite 1007 passing;
tscclean; scroll-hold confirmed in a real browser.🤖 Generated with Claude Code