Skip to content

Build: the run bar sits flush at the bottom, in one row - #1317

Merged
PavelMakarchuk merged 3 commits into
mainfrom
fix/v3-run-bar-sticky
Oct 16, 2026
Merged

PavelMakarchuk merged 3 commits into
mainfrom
fix/v3-run-bar-sticky

Conversation

@PavelMakarchuk

Copy link
Copy Markdown
Contributor

With a long reform open (for example a value per state), the sticky run bar overlapped the content oddly: content showed through a strip below the bar, the "No name yet" note sat in a second box under it, and the bar's height changed as the note came and went, which made scrolling jumpy.

  • A sticky element stops at its scroll container's padding, so bottom: 0 left the page's 16–24 px padding strip open below the bar. The bar now sticks at -padding (tw:-bottom-lg tw:sm:-bottom-2xl) and fills the strip with its own padding: nothing shows under it.
  • The "No name yet… Name it" note moved into the bar's own row, beside Discard / Save / Run, as text and a quiet button. The quick name box opens in the same place.

🤖 Generated with Claude Code

PavelMakarchuk and others added 2 commits October 16, 2026 15:36
…with the no-name note inside it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…padding

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
policyengine-calculator-next Ready Ready Preview Oct 16, 2026 8:21pm UTC
policyengine-website Ready Ready Preview Oct 16, 2026 8:21pm UTC

Request Review

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch was successfully deployed

2 active deployments
Preview – policyengine-calculator-next — bfd7e85b Deployed Oct 16, 2026 by vercel[bot]
Preview – policyengine-website — bfd7e85b Deployed Oct 16, 2026 by vercel[bot]
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.

1 participant