The Chat page's layout (ui/src/chat/chat.css) is built for a fixed, no-scroll chat window: .chat-workspace uses grid-template-rows: auto minmax(0, 1fr) auto with overflow: hidden, and only .chat-transcript (the message list) is meant to scroll. .chat-page only sets min-height: calc(100vh - 5rem), not a fixed height.
Any dynamic content injected above .chat-layout -- the status/error banner (see #443), extra status pills, a long "Reload Telegram"/"Check updates" row wrapping on a narrower viewport -- has no height budget accounted for, so it just pushes the whole grid down and grows total page height past the viewport. That breaks the intended design: the page itself scrolls instead of just the transcript.
Screenshot: Chat page with the 501 error banner (see #443) visibly adding an extra row that isn't accounted for in the fixed layout.
Expected
The top status/banner region should have a bounded height (or the page should reserve space for it) so injecting a banner or wrapping the status pills never causes page-level scroll -- only .chat-transcript should ever scroll.
Imported from beads archie-core-1786637500980-423-12a63a68 · GitHub #444 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08
The Chat page's layout (`ui/src/chat/chat.css`) is built for a fixed, no-scroll chat window: `.chat-workspace` uses `grid-template-rows: auto minmax(0, 1fr) auto` with `overflow: hidden`, and only `.chat-transcript` (the message list) is meant to scroll. `.chat-page` only sets `min-height: calc(100vh - 5rem)`, not a fixed height.
Any dynamic content injected above `.chat-layout` -- the status/error banner (see #443), extra status pills, a long "Reload Telegram"/"Check updates" row wrapping on a narrower viewport -- has no height budget accounted for, so it just pushes the whole grid down and grows total page height past the viewport. That breaks the intended design: the page itself scrolls instead of just the transcript.
Screenshot: Chat page with the 501 error banner (see #443) visibly adding an extra row that isn't accounted for in the fixed layout.
### Expected
The top status/banner region should have a bounded height (or the page should reserve space for it) so injecting a banner or wrapping the status pills never causes page-level scroll -- only `.chat-transcript` should ever scroll.
---
_Imported from beads `archie-core-1786637500980-423-12a63a68` · GitHub #444 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumbug labels 2026-10-27 13:38:25 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Chat page's layout (
ui/src/chat/chat.css) is built for a fixed, no-scroll chat window:.chat-workspaceusesgrid-template-rows: auto minmax(0, 1fr) autowithoverflow: hidden, and only.chat-transcript(the message list) is meant to scroll..chat-pageonly setsmin-height: calc(100vh - 5rem), not a fixed height.Any dynamic content injected above
.chat-layout-- the status/error banner (see #443), extra status pills, a long "Reload Telegram"/"Check updates" row wrapping on a narrower viewport -- has no height budget accounted for, so it just pushes the whole grid down and grows total page height past the viewport. That breaks the intended design: the page itself scrolls instead of just the transcript.Screenshot: Chat page with the 501 error banner (see #443) visibly adding an extra row that isn't accounted for in the fixed layout.
Expected
The top status/banner region should have a bounded height (or the page should reserve space for it) so injecting a banner or wrapping the status pills never causes page-level scroll -- only
.chat-transcriptshould ever scroll.Imported from beads
archie-core-1786637500980-423-12a63a68· GitHub #444 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08