fix(frontend): home scrolls with the page; the rail stays pinned - #5847
Conversation
dosubot
Bot
added
the
size:M
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Railway Preview Environment
Updated at 2026-08-09T21:22:35.896Z |
The returning-user home was a bounded frame with an inner scroll on the main column. Now the page itself scrolls (one scrollbar, the browser's own) and only the rail is sticky, scrolling internally when taller than the viewport - the claude.ai model. The apps-home route leaves the static full-height flag list; the first-run branch (a centered document with no rail) asks for the bounded frame itself via layoutFullHeightRequestAtom, so playground/evaluator surfaces are untouched.
…ents Mahmoud's two refinements: sticky pins the moment the element reaches its top offset, so an offset equal to the rail's resting y (the 56px gutter) pinned it from scroll zero and it never travelled - top-4 gives it 40px of travel with the page before it pins, plus a little air once pinned. And the Your agents card drops its + New agent action (the page header already carries it); All agents stays as the card's only action.
Demo workspaces render a fixed 38px banner that covered the pinned rail's top 22px. The layout sets --ag-demo-banner-h only in demo projects; the rail's sticky offset and max-height read it (0 elsewhere).
01bdd5c to
5e10fb5
Compare
b9f648f to
1518387
Compare
1 participant
The returning-user home page was a bounded frame whose main column scrolled INSIDE itself — an inner scrollbar next to a static page, which looked bad with any real number of sessions.
Now it works the way claude.ai's home does:
layoutFullHeightRequestAtom; the static route flag for apps-home is gone, so playground/evaluator and the other full-height surfaces are untouched.Stacked on #5836 (its StripHome edits build on the shared-column work there).