The Explore panes grid had an auto row, so a tall rail (Provenance + Tags + long Suggestions) grew past the fixed-height workspace and scrolled the whole page — the empty gap at the top. grid-template-rows: minmax(0, 1fr) bounds the row so panes scroll internally; reset to none in the stacked (<=1100px) layout.
The Explore panes grid had an `auto` row, so a tall rail (Provenance + Tags + long Suggestions) grew past the fixed-height workspace and scrolled the whole page — the empty gap at the top. `grid-template-rows: minmax(0, 1fr)` bounds the row so panes scroll internally; reset to `none` in the stacked (<=1100px) layout.
`d63dfa5`, green on dev (run 1540).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The panes grid had no explicit row, so the implicit `auto` row sized to its
tallest pane's content. With Provenance + Tags + a long Suggestions list, the
rail outgrew the fixed-height workspace, spilled over and made the WHOLE page
scrollable — showing as a weird empty gap at the top (operator-flagged
2026-06-26). grid-template-rows: minmax(0, 1fr) bounds the row to the container
so each pane's own overflow-y:auto scrolls internally instead. Reset to `none`
in the stacked (<=1100px) layout where the page is meant to scroll.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 Explore panes grid had an
autorow, so a tall rail (Provenance + Tags + long Suggestions) grew past the fixed-height workspace and scrolled the whole page — the empty gap at the top.grid-template-rows: minmax(0, 1fr)bounds the row so panes scroll internally; reset tononein the stacked (<=1100px) layout.d63dfa5, green on dev (run 1540).🤖 Generated with Claude Code