fix(ui): eliminate phone footer safe-area strip#1265
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
📝 WalkthroughWalkthroughThe mobile search footer backdrop now uses transparent terminal rendering, revised blur and tint masks, and delayed visibility hiding. CSS contract and UI tests verify the updated paint, opacity, visibility, reduced-motion, and scroll-hidden behavior. ChangesPhone footer paint behavior
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/branch-review-ledger.md`:
- Line 1108: Correct the date in the ledger entry for commit
e1657a4a4e3e25b4a35a1dcf544b3efddb123c3f to the actual review date, July 26,
2026, or defer adding the entry until July 27 after the review occurs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: cdf0ceb4-b79c-485e-9134-feffcd93549c
📒 Files selected for processing (5)
docs/branch-review-ledger.mddocs/search-chrome-behaviour.mdsrc/app/globals.csstests/mobile-chrome-paint-contract.test.tstests/ui-phone-scroll.spec.ts
Summary
Verification
npm run verify:pr-localnpm run verify:uiVerification not run:
npm run verify:release; risk-scoped coverage used the complete 314-test Chromium production UI suite plus focused WebKit safe-area/compositor cases. No live OpenAI, Supabase, Railway, or deployment check was run.Risk and rollout
mainwill trigger the repository's normal Railway auto-deploy; no direct Railway mutation is performed here.Clinical Governance Preflight
Not applicable: presentation-only CSS, browser tests, and documentation. No ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, environment, or clinical-output behavior changes.
Notes
RAG impact: no retrieval behaviour change — CSS, browser/static test coverage, and search-chrome documentation only.
Summary by CodeRabbit
Bug Fixes
Documentation
Tests