Skip to content

fix(ui): opaque session banner + header stacking context#404

Open
dimakis wants to merge 1 commit into
mainfrom
fix/session-banner-bg
Open

fix(ui): opaque session banner + header stacking context#404
dimakis wants to merge 1 commit into
mainfrom
fix/session-banner-bg

Conversation

@dimakis

@dimakis dimakis commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • Session banner used undefined --bg-primary CSS variable (resolved to transparent), causing scrolled content to bleed through
  • Header toolbar had no stacking context, so scroll content could render above it
  • Top padding on .chat-messages created a transparent gap between header and sticky banner

Changes

  • Replace var(--bg-primary) with var(--surface) on .session-banner
  • Add position: relative + z-index: 20 to .chat-header
  • Move top padding from .chat-messages to bottom-only, so sticky banner sits flush
  • Horizontal negative margin on banner to span full scroll container width

Test plan

  • Open a session in mobile Safari — no content bleeds through header or banner
  • Scroll up/down — banner sticks flush, no transparent gap
  • Check desktop layout is unaffected
  • Verify keyboard-open state still compacts header correctly

🤖 Generated with Claude Code

The session banner used undefined --bg-primary (resolved to transparent),
so scrolled content bled through behind it and the header toolbar.

- Replace var(--bg-primary) with var(--surface) on .session-banner
- Add position:relative + z-index:20 to .chat-header so scroll content
  never renders above it
- Remove top padding from .chat-messages so the sticky banner sits flush
  against the header with no transparent gap
- Horizontal negative margin on the banner to span full scroll width

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

@dimakis dimakis left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Centaur Review

LGTM — no issues found.

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