fix(header): drop no-op backdrop-blur that flickered content on scroll

[michaelassraf]

Problem

Reported: a visible flicker when scrolling the flamingo /pricing page, worst as the large monospace headings (`What's in OpenFrame:`, `One Dollar. One Device.`) pass under the sticky header.

Root cause

The flicker is not in the page content — that section is static on scroll (instrumented: 0 DOM mutations, no reveal/entrance animations, opacity 1, no transforms). It's a compositor artifact from the shared sticky header.

The header carried `backdrop-blur-sm`, but every platform ships an opaque header background (`headerBackground: UNIFIED_HEADER_BG = 'bg-ods-bg'`, live-computed `srgb 0.086…`, alpha 1; others use `bg-ods-card`). So the blur samples a backdrop that is then fully painted over — zero visual effect, but it still forces Chromium to:

• keep a `backdrop-filter` compositing surface on the sticky bar, and
• re-rasterize the strip behind it every scroll frame.

That backdrop snapshot desyncs by a frame against the scrolling content → content flickers as it passes under the header. It's worst on high-contrast large text (the pricing headings). Flamingo also has `headerAutoHide: false`, so the header never translates on scroll here — ruling out the show/hide transform and leaving the backdrop-filter as the sole culprit.

Fix

Remove `backdrop-blur-sm` from the header, with a comment explaining why it must not return (and how to add a real translucent "glass" header deliberately if ever wanted). This is a visual no-op on every platform (all header backgrounds are opaque) and eliminates the flicker for all header-bearing platforms at once.

Verification

• Header renders pixel-identical: `backdropFilter: none`, background/border unchanged.
• Confirmed on local dev that the scroll flicker is gone on /pricing.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@michaelassraf, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bd4d736a-c6b5-49ea-8e71-4bf1ab46bdc6

📥 Commits

Reviewing files that changed from the base of the PR and between dae3088 and dae27d9.

📒 Files selected for processing (1)

• openframe-frontend-core/src/components/navigation/header.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/pricing-scroll-flicker-94bb6e

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}