Skip to content

fix(tangle-cloud): opaque chrome — drop glassmorphism on nav/strips/toolbar#3243

Merged
tangletools merged 1 commit into
developfrom
feat/opaque-nav-chrome
May 25, 2026
Merged

fix(tangle-cloud): opaque chrome — drop glassmorphism on nav/strips/toolbar#3243
tangletools merged 1 commit into
developfrom
feat/opaque-nav-chrome

Conversation

@drewstone
Copy link
Copy Markdown
Contributor

The fixed top bar, the blueprint identity strip, and the page toolbar all used a semi-transparent background + backdrop-blur, so page content bled through them on scroll. Makes all three fully opaque (solid bg-elevated / bg-background, no blur).

  • Header.tsx — top bar: bg-[var(--bg-elevated)]/85 … backdrop-blur-mdbg-[var(--bg-elevated)].
  • IframeBlueprintLayout.tsx — blueprint identity strip: bg-background/95 … backdrop-blur …/70bg-background.
  • PageToolbar.tsx — search/filter toolbar: same → bg-background.

The pills in the nav are untouched (you liked them).

Test plan

  • full pre-push (lint/test/build) passed
  • Visual: scroll any page — chrome is solid, nothing shows through

…oolbar

The fixed top bar, blueprint identity strip, and page toolbar used
semi-transparent backgrounds + backdrop-blur, so page content showed through
them on scroll. Make all three fully opaque (solid bg-elevated / bg-background,
no blur) so they read as solid chrome.
@drewstone drewstone requested a review from AtelyPham as a code owner May 25, 2026 19:33
Copy link
Copy Markdown
Contributor

@tangletools tangletools left a comment

Choose a reason for hiding this comment

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

Opaque chrome, pills preserved. Approving.

@tangletools tangletools merged commit c96c22c into develop May 25, 2026
7 checks passed
@tangletools tangletools deleted the feat/opaque-nav-chrome branch May 25, 2026 19:33
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