Repository navigation
feat(chat): let the board-view sidebar grow past 1400px on wide windows - #14870
Conversation
UX Review (Opus 5.5, fork) — 🟡 CONCERNSUX-level review of UX-Verdict: CONCERNS Switching between list and board view now snaps the sidebar between 1400 and up to 2884 px. No recording shows that jump, and no first-time reader has seen these states. Watch
[UX-REVIEWED] 8632faf Description read[DESCRIPTION-READ] 1ffdf8bb47a75c3d52ad55ab3e5a692a4c1a4c9c26d7f0dd83556ca3b0826daa That sha256 names everything this verdict read: the PR description, plus the 9 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Design Review (Opus 5.5, fork) — ✅ PASSDesign-level review of Design-Verdict: PASS Confirm that existing board users accept a narrower board on mid-width windows: a saved 1400 on an 1800 px window now paints 1244 px. [DESIGN-REVIEWED] 8632faf Description read[DESCRIPTION-READ] e84be823f29a16b25c30f542e5a08d9ccdbc3354e61fdd7afd5f1664d570ccf3 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
First Principles Review (Opus 5.5, fork) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Check that the board-column Playwright specs still pass at the 1244 px paint on head 8632faf. The E2E run the description cites ran on 8a794f4. What this change shipsInventory (10 items) — 10 justifiedIntent: let users of board view on ultra-wide windows drag the session sidebar past 1400 px. This is an ADDITION; it also fixes the narrow-window overhang in #16094.
[FIRST-PRINCIPLES-REVIEWED] 8632faf Description read[DESCRIPTION-READ] 8995ba3034b8245cc3c1ccc5b079ef648549050895f2a742d71560fbb7418439 That sha256 names the PR description this verdict read. Recompute it with |
Opus 5.5 Review (fork) — ✅ no blocking findingsReviewed |
ab633ec to
ad7940f
Compare
|
CI status for head ad7940f (rebased onto main 7610731 to pick up #14883, which fixed the
A fresh head once the installation rate limit clears should rerun the review lanes. |
ad7940f to
934f71e
Compare
|
Dispositions for the reviews of Opus 5 finding 1: ChatSidebar.tsx drag ceiling vs the painted column. Fixed. After a drag to 2884 on a 3440 px window, a mid-session narrowing left the root at Opus 5 finding 2: useRailWidth.ts Design Review note: a max-width drag with a side panel open. No change needed. UX Review Watch: fork-lane cap, no first-time blind read. Acknowledged. The screenshots still cover every drag state this PR changes, and the handle and its copy are unchanged. The narrowed-window case this head adds cannot be shown in one static frame, so its test covers it. The blind read would need a maintainer to push the branch to this repository. GPT 5.6 / First Principles: no findings on The product question on #14853 about an arbitrary share versus a fraction, and a persisted bound, is still open for the issue author. This PR does not settle it. It implements the window-relative ceiling described above. |
934f71e to
83a4031
Compare
|
|
|
|
|
|
|
|
|
|
|
|
Dispositions for head d1c5745 (code delta from baedb1d: First Principles, item 5 (rail first frame): fixed by subtraction. First Principles, item 4 (keeping a wider saved width): kept, Goal amended. The PR body's Goal now states it: a width saved on a wide window is a saved preference, painted as wide as a narrower window allows and left saved for the wide one. Main already has this rule in UX, chat pane faint in image 2: fixed. Image 2 was recaptured on this code at 3440 px with no dialog or scrim open (the capture script checks that before the shot); the chat pane is fully legible. UX, image 7 from an earlier head: fixed. Recaptured on this code (now image 6): 2884 saved, 1200 px window, sidebar paints 644 px, handle on screen, UX, a full-width drag leaves a 320 px chat pane: by design, no change. 320 px is the existing UX, saved width outlasts a narrower window: intended, now in the Goal. Same rule as First Principles item 4 above. UX, no first-time reader has seen the drag: a cold read by a maintainer is outside what the author can supply; every state is in the screenshots. |
|
Dispositions for head f53666c (code delta from d1c5745: First Principles, item 6 (move-skip guard): fixed by subtraction. UX, "a saved wide width comes back unexpectedly": no change, the suggested rule already holds. A drag on a narrow window that ends below the room the window allows saves that width: the only drag that saves nothing is one that ends exactly where it started, which on a narrowed window is also the room itself. A drag that ends at its own start changed nothing on screen, so the wide monitor keeps the width the user last set there. The PR's Goal now states this rule. UX, the 320 px chat pane at the new maximum: the review marks this as a product decision for a human, not a defect. 320 px is the existing |
|
Dispositions for head e11af60 (rebased onto main 4e0aa9b; code delta from f53666c: UX, rows stretched across very wide sidebars: fixed with the suggested row cap. Past 1400 px the tree, flat and conductor lanes take the extra width as inline-end padding ( First Principles, item 4 (stored vs painted width): kept, Goal now names it. The Goal states that a saved width wider than the current window survives a drag or nudge that ends where it started, and cites the Opus 5 BLOCKING finding at UX, no first-time reader has seen the drag: a cold read by a maintainer is outside what the author can supply; every state is in the screenshots. |
|
Dispositions for head 70afd09 (code delta from e11af60: First Principles, item 9 (optional UX, list view detached at wide widths: fixed with the suggested alignment. The cap moved from the lane to the sidebar root: in the list views (tree, flat, conductor) the root insets its content by the width past 1400 ( UX suggestion, keep the list-view drag ceiling at 1400: not taken in this head. #14853 asks for the session list as well as the board to grow on wide screens, and the list content now stays readable at any width. Whether a list-view drag past 1400 should be allowed at all is a product call for a maintainer. UX, no first-time reader: a cold read by a maintainer is outside what the author can supply. |
|
|
|
Replies to the head 70afd09 review items, all addressed in head dcf4b26 (one commit on main 105630f):
|
|
UX review disposition, new head caaa761 (reviewed head dcf4b26). Width jumps when you switch views: fixed. A switch between list and board view now eases the sidebar root's The chat pane can shrink to its minimum: as intended, and now held on every window. This head also holds every painted sidebar width, on either side of 1400, to the room beside the nav rail and a 320 px chat pane, so a sidebar can never push the chat pane below that minimum (before this head a saved 1400 on a 1200 px window still did). Whether 320 px is a usable chat pane at full drag is the existing No first-time reader has read the screenshots cold: that is a maintainer-run step I cannot do as the author. The screenshots and the manual-verification table in the description cover each state, including the new 1200 px row. |
|
Dispositions for the reviews of caaa761, new head 8a794f4. UX BLOCK, no recording of the view-switch ease: fixed. The description now carries two recordings (item 5) on a 3440 px window with 2884 saved: board to list to board at real speed, and the same switch with CSS animations slowed to 0.1x. Sampled root widths on the way down were 2884, 2382, 1960, 1633, 1431, 1400, so it is one element resizing, not a swap. The two Watch items: the lane strip clipping at 1200 px is the board's existing horizontal scroll, unchanged by this PR, and the cold read is a maintainer-run step I cannot do as the author. Design, the chat-pane reserve upstream of the clamp: kept, with both clear conditions met. The board-column Playwright specs ( First Principles item 9, First Principles item 6, the 150 ms ease: kept. This PR causes the jump it smooths. Main never stored a width above 1400, so main never moved a list/board switch from 2884 to 1400. The UX lane flagged that jump as a regression this PR ships, and the recordings show the ease turning it into a visible resize. An instant resize is right for a drag, because the pointer is the continuity there. A view switch has no pointer motion, so nothing else ties the two widths together. The ease costs one state pair, one timer and the Frontend Lint, unit literal at Backend Tests (Windows) (2): |
|
Dispositions for the reviews of 8a794f4, new head 932c39e (rebased onto main af1eb61, still one commit). First Principles item 9, First Principles item 4, the narrow-window paint and the deleted e2e pin: both clear conditions addressed. Both board-column Playwright specs ( UX Watch 1, the third lane cut off with no sign it scrolls: fixed. The lane strip now measures itself with UX Watch 2, the chat pane at 320 px on a wide window: kept. 320 px is UX headline, no first-time reader: that cold read is a maintainer-run step I cannot do as the author. Backend Tests (Windows) (7) |
|
Dispositions for the reviews of 932c39e, new head 70be56b. UX Watch 1, the edge fade too faint: fixed. The fade is now 48 px wide and starts from the page background, which is darker than the lane cards, so the clipped titles fade into a visible shadow instead of into the same colour. Images 8 and 9 in the description are re-captured on this head (same 1200 px board, strip UX Watch 2, the cold read of list view shrinking a wide board width: that read is a maintainer-run step I cannot do as the author. What the user sees is covered: the saved board width is never rewritten by a switch, board view paints it again on return, and the switch eases on the side panel's width curve so it reads as a resize rather than a reset. First Principles item 6, the view-switch ease: kept, with its surface cut. This PR causes the jump the ease covers: main never stored a width above 1400, so on main a list/board switch never moved the sidebar from 2884 to 1400. The ease no longer has its own spelling. Design Watch 1, Design Watch 2, Backwards compatibility: the description's section now lists every reader of Backend Tests (Windows) (5) on 932c39e: |
|
Dispositions for the reviews of 70be56b, new head 0c91ab0. First Principles item 8, the view-switch ease: removed. You are right that main already repaints at once on a view switch ( UX Watch, the right-edge fade barely shows: fixed. The fade on both edges is now 64 px and holds the page-background tone over its outer 15 percent before it clears, so the clipped Done lane's titles visibly dim at the right edge, as the Planned lane's do at the left. I checked the strip's pixels on both captures: the two gradients are mirror images, and nothing sits on top of the right one. Images 8 and 9 and the enlarged right-edge crop are re-captured on this head. UX headline, no first-time reader: a maintainer-run step I cannot do as the author. Local on this head: |
|
The core change is coherent. The stored width and the painted width are tracked separately, list views keep the 1400 cap, and the tests cover drag, nudge and the board e2e geometry. Most of the 119 files are a one-line |
|
@iamwhatever thanks. Both scope additions are out of this PR and in the follow-up #17136, so each can be judged on its own. New head 5b808e2 (rebased onto main c6bfd72, still one commit).
First Principles item 6 on 0c91ab0 (the edge fade as a second feature): fixed by that removal; every part the subtraction listed is gone from this PR. UX Watch items on 0c91ab0 (light theme not shown, the fade over the clipped lane's header buttons): both are about the fade, which this PR no longer ships. They are answered on #17136, whose light-theme frames show the clipped lane fading out at the right edge and, once scrolled, at the left. The UX headline item (no first-time reader) is a maintainer-run step I cannot do as the author. Local on this head: |
|
Dispositions for the UX and First Principles reviews of 5b808e2 (no new head: neither item has a change that belongs in this PR). UX Watch 1, the clipped lane at a 1200 px paint has no sign it scrolls: this is the edge fade, which moved to #17136 at a maintainer's request so it can be judged on its own. #17136 now carries the source for it on head 5eb6830 ( UX Watch 2, a drag to the ceiling on a 3440 px window leaves the chat pane 320 px: kept. The board-view ceiling is UX, no first-time blind read: that read is a maintainer-run step that the author cannot do from a fork. First Principles item 8, make The two lanes stay CONCERNS for a maintainer to rule on; nothing else on this head is open. |
|
Dispositions for the First Principles and UX reviews of 5b808e2. New head 8a3e9a3 (one commit, rebased onto main e281eca). First Principles item 8, the required UX Watch 1, a lane clipped at a 1200 px paint has no sign it scrolls: that cue is #17136, split out at a maintainer's request. Its new head 4c1f0b8 also answers the UX finding there: the edge chevron is now a labelled button that scrolls the strip by one lane. UX Watch 2, a drag to the ceiling on a 3440 px window leaves the chat pane 320 px: kept, as on 5b808e2. The board-view ceiling is UX, no first-time blind read: a maintainer-run step that cannot be supplied from a fork. For #17136's UX note asking that this PR carry evidence of a board sidebar past 1400 px: image 7 in the description shows board view on a 3440 px window dragged to 2884 px ( Also in this head: a test that a board view on a 1200 px window with 1400 saved tells the host 1200 - rail - 320, then 1400 once the window widens to 3440 (it fails when the report sends the seat width instead of the painted width). |
In board view the drag, arrow-key nudge and aria-valuemax use the room beside the live nav rail and a CHAT_PANE_MIN_W chat pane (sidebarRoomWidth), the same function that holds the paint. The list views cap at SIDEBAR_MAX, since they gain nothing from a wider sidebar, and reserve only the nav rail, as the drawer's own clamp does. useSidebarResize takes boardActive and reports the width the root paints at to ChatPage from one layout effect, and ChatPage seats the drawer at that width. ChatPage reads the stored width at most SIDEBAR_MAX until that report, and holds the collapsed sidebar's recents flyout, a session list, to SIDEBAR_MAX. A width past SIDEBAR_MAX saved in board view is kept as saved: list view paints it at SIDEBAR_MAX and board view paints it again. In board view every painted width, on either side of SIDEBAR_MAX, is held to the room beside the rail and a minimum chat pane (sidebarRoomWidth), so a saved 1400 and a saved 1401 paint the same on a narrow window, the chat pane keeps its minimum, and the root and its resize handle stay inside the drawer. The drag ceiling and aria-valuemax are held to the same room, read from the live window width. A drag or nudge starts from the painted width. The sidebar and ChatPage read that width from one store (useWindowWidth, on the window's resize event), so both paint against the same width in the same render and no caller passes it in. commitResize is the one place a drag or nudge saves: a resize that ends on the painted width it began from (a press with no travel, or pushing against the ceiling) keeps the stored preference. The mobile drawer and the sessions embed stretch the sidebar to their own width, so their paint reserves no chat pane (fillsHost). The header's compact and tiny collapse and the board auto-widen read the painted width. Closes kirodotdev#14853
|
Dispositions for the UX review of 8a3e9a3. New head 8632faf: the same tree, re-headed to rerun one Windows shard. UX Watch, no first-time reader: the lane says it cannot go above CONCERNS without one, and that read is a maintainer-run step that cannot be supplied from a fork. UX Watch, clipped board lanes on narrow windows with no hint: the edge fade is #17136, split out at a maintainer's request; it is ready to land right after this PR. CI on 8a3e9a3: the one red, |
|
Reviewed again at the new head, still not approving (crew-pr-reviewer). This is a UI feature (+689/-80), and it needs a maintainer's or design review. |
bolichen97
left a comment
There was a problem hiding this comment.
Reviewed on behalf of the maintainers (sweep 2026-10-06): full diff read, callers verified against current main, readiness passed, required checks green, no blocking review threads. Product note accepted on the maintainers' behalf: in board view the painted sidebar now reserves a 320px chat pane, so a manually widened board sidebar on ~1636-1956px windows paints up to 156px narrower after upgrade (saved preference kept). The two scope additions iamwhatever held on were removed to #17136. Approving and merging.
Problem / Motivation
Goal: In board view on a wide window the session sidebar can be dragged wider than 1400 px, as far as the window allows while the chat pane keeps its minimum width. The list views (tree, flat, conductor) keep the 1400 px ceiling, since a session list gains nothing from a wider sidebar. A width saved in board view is a saved preference like any other: list view paints it at 1400, board view paints it again, and a narrower window paints it as wide as that window allows and leaves it saved. Main already treats the stored width this way (
ChatPage: "clamp for render but leave the preference for the wide viewport"); this branch keeps that rule for widths above 1400, which main never had to store. That makes the stored width and the painted width two separate values, and a saved width wider than the current view or window survives a drag or nudge that ends where it started. The Opus 5 review blocked onresize.ts:98on head 2af8364 for exactly that: a nudge that changed nothing replaced the wider saved width with the painted one, so keeping the two values apart is what stops this branch shipping that regression.One paint rule holds on both sides of 1400 in board view: every painted width is held to the room beside the nav rail and a minimum chat pane, so on a 1200 px window a saved 1400 and a saved 1401 paint at the same width and the chat pane keeps its 320 px minimum. Without it, a saved 1400 painted as stored while a saved 1401 was held to the room, so the width jumped at the 1400 boundary and a board drag to 1400 squeezed the chat pane below its minimum. This also removes the narrow-window overhang tracked in #16094. It changes one pinned geometry on purpose: the board-column Playwright specs (
session-tags-folders,session-tags-e2e) prime a stored 1400 on an 1800 px viewport, and main'sclampSidebarWidthtest pinned that the drawer stays 1400 there, because reserving the chat pane in the clamp alone once made the drawer 1244 px around a 1400 px root and broke both specs. On this branch the root and the drawer both paint 1800 - 236 - 320 = 1244 px, so they agree, and the newboard-column e2e geometrytest inclampSidebarWidth.test.tspins that pair. Both specs ran and passed at that paint in the E2E job on head 8a794f4 (job; the harness allows no skipped spec).A switch between list and board view repaints the root at once, as main's board auto-widen and its restore already do.
SIDEBAR_MAX = 1400inwebsite/src/pages/chat/sidebarWidth.tsis an absolute ceiling. The pointer drag and the arrow-key nudge both clamp to it, and every stored-width reader throws away a saved value above it. On a 3440 px window a board view's lanes stop at 1400 px, about 40% of the window, and at 5120 px at about 27%, althoughclampSidebarWidthandpanelReservecould seat a much wider sidebar beside aCHAT_PANE_MIN_Wchat pane.Why it matters
On ultra-wide monitors most of the window goes to a single transcript while the board view's lanes stay cramped, and there is no setting that lifts the sidebar ceiling. Settings > Chat > Content Width > Full only widens the transcript.
Not a goal
SIDEBAR_MAXas their ceiling and paint a wider saved width at 1400.boardSidebarWidthkeeps itsSIDEBAR_MAXceiling; the user can drag the board wider by hand).Screenshots / video
Each image is described in the sentence above it. Images 1 and 4 are from a headless Chromium against an isolated gateway built from the named code. Images 2, 3, 6 and 7 were captured on head dcf4b26, whose paint for these states this head keeps, from the repo's isolated ChatPage capture entry (the real
ChatPageandChatSidebar, six fixture sessions, a fixture transcript and, for board view, three fixture lanes that each match every fixture session; API answered by fixtures, served by the website's vite dev server on 127.0.0.1); the 236 px column on their left is a blank stand-in for the nav rail, the width the app reserves for it. No dialog or scrim is open in any frame (checked in the capture script before each shot).mc-sidebar-width1400,aria-valuemax1400), as on main. The list views gain nothing from more width, so their ceiling is unchanged.mc-sidebar-width2884,aria-valuemax2884), the three lanes share the width, and the chat pane keeps its 320 px minimum on the right. In list view the same saved 2884 paints the sidebar at 1400 px and stays saved (a separate capture withmc-sidebar-width2884 at 3440 px: root 1400 px,aria-valuenow1400,mc-sidebar-widthstill 2884).mc-sidebar-widthsaved as 2884 and the window loaded at 1200 px: the sidebar paints at 644 px (1200 - 236 rail - 320 chat pane) with its header, search box and lanes, the resize handle is on screen at its right edge, andmc-sidebar-widthstill reads 2884.ChatSidebar.resizeTouchandclampSidebarWidthtests listed below.Image 4 (before): 1440 px window, stored 1400, overhang on main
Manual verification
From the capture entry above, driving the handle with a headless Chromium mouse drag on this head:
aria-valuemax1400aria-valuemax2884, chat pane 320ChatSidebar.resizeTouch)ChatSidebar.resizeTouch)What changed (motivation → approach → change)
sidebarRoomWidth({ winW, railW, chatMin }), is the room beside the live nav rail (useRailWidth) and aCHAT_PANE_MIN_Wchat pane, floored atSIDEBAR_MIN. In board view it holds the paint and is the drag ceiling; the list views take the smaller ofSIDEBAR_MAXand the room beside the rail alone. A raised fixed cap would be wrong on the next wider screen and could push the chat pane below its minimum.chat-sidebar/resize.ts:useSidebarResizetakesboardActiveandfillsHost, and reads the live window width fromuseWindowWidth, the one storeChatPagealso reads (a new hook inhooks/useWindowWidth.ts, on the window'sresizeevent), so the sidebar and the drawer paint against the same width in the same render and no caller passes it in. The drag, the arrow-key nudge andaria-valuemaxuse that ceiling, read at call time through refs.ChatSidebarcalls the hook afteruseBoardColumns(the pinned hook order inChatSidebar.ownerComposition.test.tsmoves with it).SIDEBAR_MAX,sidebarPaintWidthholds it to the room, and one layout effect reports the painted width toChatPage, which seats the drawer at it through main'sclampSidebarWidth(the mobile drawer and the sessions embed reserve no chat pane). A saved 2884 paints 1400 in list view and 2884 in board view, and switching never rewrites it.ChatPage's first read and the collapsed recents flyout are held to 1400.parseStoredSidebarWidth(raw)replaces the three copies of theSIDEBAR_MIN..SIDEBAR_MAXcheck and keeps a wider saved width.commitResizeis the one place a drag or nudge saves, and a resize that ends on the painted width it began from keeps the stored preference.Backwards compatibility
Compatible: the
mc-sidebar-widthkey and its format are unchanged. Every value main accepts still loads as the same width on the same window in list view; board view now paints it beside the chat pane's minimum, so on a window too narrow for both it paints narrower than on main and stays saved. A value above 1400, which main discarded, now loads as saved, paints at 1400 in list view, and paints beside a minimum chat pane in board view.Readers of the stored width, and how each still works:
ChatPage's first read (beforeChatSidebarreports its seat): reads the value throughparseStoredSidebarWidth, held to 1400, so a board-view width never widens the first frame or the collapsed recents flyout.useSidebarResize(mc-sidebar-widthandmc-sidebar-width-pre-board): reads any value at or aboveSIDEBAR_MINas saved; the paint, not the reader, holds it to the view and the window.clampSidebarWidth.test.ts; both specs passed at that paint in CI).Rolling back to a build without this change: its readers drop a stored value above 1400 and fall back to 260 px, so a board width saved past 1400 resets once; values at or under 1400 load as before.
Tests
website/src/test/ChatSidebar.resizeTouch.test.tsx:list view ceilingblock, 3440 px window: a drag to the far right stops atSIDEBAR_MAX, saves 1400 and reportsaria-valuemax1400; a saved 2884 paints at 1400, the host is told 1400, and an ArrowRight plus a drag pushed right both keep the saved 2884; switching list to board to list paints 1400, 2884, 1400, 2884 and keeps the saved 2884 throughout; board view still accepts a drag from 1400 to 2884 and saves it. The first three fail on head 70afd09 (the list view dragged to 2884 and painted the saved 2884 with an inset).board view window-relative drag ceilingblock (the earlier window-relative cases, now rendered in board view): at 3440 px and 5120 px a drag passesSIDEBAR_MAXand leaves exactlyCHAT_PANE_MIN_Wfor the chat pane; nudges stop at the same ceiling; a width saved at 3440 px paints beside a minimum chat pane on a 1440 px window and comes back when the window widens; a window narrowed after a wide drag paints inside the drawer and drags from there; a press with no travel, a pen's zero-delta moves, a swallowed nudge and a drag pushed against the ceiling each keep a wider saved width; a nudge that does move saves;fillsHostreserves no chat pane; a wide saved width painted narrow gets the tiny header; at 1440 px the ceiling andaria-valuemaxare the room beside the rail and a minimum chat pane; at 1200 px a saved 1400 and a saved 1401 paint the same in list view (beside the rail) and in board view (beside the rail and a minimum chat pane); both fail with the oldstored <= SIDEBAR_MAXearly return. A board view on a 1200 px window with 1400 saved tells the host 1200 - rail - 320, then 1400 once the window widens to 3440; this fails when the report sends the seat width instead of the painted width.website/src/test/ChatPage.previewExpandSessions.test.tsx: with 2884 saved on a 3440 px window and the sidebar collapsed, the recents flyout opens 1400 px wide and the saved width stays; this fails on head ad75048 (the flyout opened 2884 px wide).website/src/test/ChatSidebar.persistenceContract.test.tsx(stored-width cases now run on a 2400 px window, wide enough for 1400): a stored 1401 loads as saved and paints at 1400 in list view; switching to board view with 2884 saved on a 1440 px window writes no pre-board width and keeps 2884.ChatSidebar.resizeTouch.test.tsxmoves the window by settinginnerWidthand firingresize, the eventuseWindowWidthlistens to, so every width case drives the real update path. No other test or capture fixture changes:ChatSidebartakes no window-width prop.website/src/test/clampSidebarWidth.test.ts: the board-column e2e geometry (stored 1400 at 1800 px paints the root and the drawer at the same 1244 px),sidebarRoomWidthat 1440 / 3440 / 5120 px,parseStoredSidebarWidthaccept / reject cases,sidebarPaintWidthat and pastSIDEBAR_MAX, including a 1200 px window where 1400 and 1401 paint the same (fails with the old early return), and a drawer width built fromsidebarPaintWidththenclampSidebarWidththat leaves exactly the chat minimum.Run locally on this head (one commit on main e281eca): every vitest file under
src/test/ChatSidebar*,src/test/ChatPage*,clampSidebarWidthandsidePanelFillWidth, plusintegration/ChatSidebar*(199 files, 2181 tests passed);npx tsc -b,npx eslinton the changed files,check-phantom-classes,check-theme-colorsandcheck-restyle-ratchet: clean. The board-column Playwright specs passed at the 1244 px paint in CI's E2E job on head 8a794f4 (link above).Related Issues
Closes #14853
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement