Skip to content

fix(web): keep sticky workspace headers opaque - #1207

Merged
tiann merged 1 commit into
tiann:mainfrom
swear01:agent/fix-sticky-workspace-header
Jul 28, 2026
Merged

fix(web): keep sticky workspace headers opaque#1207
tiann merged 1 commit into
tiann:mainfrom
swear01:agent/fix-sticky-workspace-header

Conversation

@swear01

@swear01 swear01 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

What changed

Give sticky workspace headers an opaque app background.

Why

When sessions scroll beneath a sticky workspace header, the header previously remained transparent. Session titles and status text showed through and overlapped the workspace name. This became especially visible after the narrow-sidebar layout from #1029 landed on main as 3cfb2ea.

The existing hover background remains unchanged.

Impact

Scrolling sessions are visually covered by the pinned workspace header instead of rendering through it.

Verification

  • bun typecheck
  • bun run test (CLI: 1,524 passed; web: 1,560 passed; shared: 142 passed; hub passed)
  • git diff --check

@swear01
swear01 marked this pull request as ready for review July 28, 2026 09:53

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Findings

  • No issues found.

Questions

  • None.

Summary

  • Review mode: initial
  • Reviewed the full diff for web/src/components/SessionList.tsx. No blocker/major/minor findings on the added opaque sticky header background. Residual risk: visual-only change, so automated review cannot confirm every theme/viewport rendering state.

Testing

  • Not run (automation). PR reports bun typecheck, bun run test, and git diff --check.

HAPI Bot

@tiann
tiann merged commit 83fc9cd into tiann:main Jul 28, 2026
3 checks passed
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.

2 participants