Skip to content

fix(app): side panels no longer cover the chat; resizable; chat fills the width - #31

Merged
httpsphl merged 1 commit into
mainfrom
fix/panels-layout
Sep 29, 2026
Merged

httpsphl merged 1 commit into
mainfrom
fix/panels-layout

Conversation

@httpsphl

Copy link
Copy Markdown
Owner

Problem

With the About (Details) or Files panel open, the chat text ran under the panel. The chat section could not shrink below its own content (min-width: auto on a flex item), so it overflowed the space left for it and, being relative, painted over the panel. The panels also had a fixed width, and the chat was a centered 48rem column, which left a lot of empty space on the left.

Change

  • ChatView gets min-w-0, so it shrinks with the panel. Reproduced at the reporter's window width (chat section 456 px inside a 257 px tab panel) and checked after the fix (both 337 px, panel right after it).
  • New ui/SidePanel: Details and Files share it. Drag the left edge, or use ←/→ (Shift for bigger steps); double click resets. 256–900 px, and CSS keeps at least 22rem for the chat. The width is kept per panel in localStorage. The drag divides by the window's zoom, so it follows the pointer at any size.
  • The chat and its composer fill the width, left-aligned, instead of a centered column.
  • Spec 15.1 and 15.3.

Tested

pnpm check (118 tests; three new for resizing and its limits). Checked in the dev preview: no overlap, drag from 320 to 480 px stored the width, chat fills the space with the panel closed.

Not in this PR

The crews sidebar is still fixed-width, and at very narrow windows the bot header squeezes the name. Both would be their own change.

… the width

The chat section could not shrink below its content, so an open panel sat
under it. Details and Files now share a SidePanel the owner drags (or
arrows) to resize, remembered per panel, and the chat is no longer a
centered 48rem column. Spec 15.1, 15.3.
@httpsphl
httpsphl merged commit f2d1ff5 into main Sep 29, 2026
3 checks passed
@httpsphl httpsphl mentioned this pull request Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant