Skip to content

fix: tighten the gap between the page menu and the tab menu - #651

Merged
TheSevenPens merged 1 commit into
masterfrom
fix/nav-spacing
Sep 2, 2026
Merged

fix: tighten the gap between the page menu and the tab menu#651
TheSevenPens merged 1 commit into
masterfrom
fix/nav-spacing

Conversation

@TheSevenPens

Copy link
Copy Markdown
Owner

The two menus are one navigation block — the page above, that page'"'"'s tabs below — but they were separated by enough space to read as two unrelated bands.

Three values, three files

None of them individually looked wrong, which is why the gap survived this long:

WordmarkNav item margin bottom 31 kept at 1 so the row still separates when it wraps on a narrow window
wordmark bar grid margin bottom 20
content host padding top 40

Eight pixels out of nine. What remains is the type'"'"'s own leading, which would need a negative margin or a LineHeight override to trim — both risk clipping descenders on "mapping" and "pressure", so they are not worth it for the last few pixels. Happy to go further if you want it tighter still.

Note

The content padding is shared, so pages with no tab menu (Home, Scribble) move up by the same amount and stay aligned with the pivoted ones — worth checking that reads right to you, since it is the one part of this that touches pages the request was not about.

Verified live on tablet (5 tabs), settings (5 tabs) and home (no tab menu).

🤖 Generated with Claude Code

The two menus are one navigation block -- page above, that page's tabs
below -- but they were separated by enough space to read as two
unrelated bands.

Three values sat between them, in different files, none individually
obviously wrong:

  WordmarkNav item margin   bottom 3 -> 1   (kept 1 so the row still
                                             separates when it wraps on
                                             a narrow window)
  wordmark bar grid margin  bottom 2 -> 0
  content host padding      top    4 -> 0

Eight pixels out of nine. What is left is the type's own leading, which
would need a negative margin or a LineHeight override to trim -- both
risk clipping descenders on "mapping" and "pressure", so they are not
worth it for the last few pixels.

The content padding is shared, so pages with no tab menu (Home,
Scribble) move up by the same amount and stay aligned with the pivoted
ones.

Verified live on tablet, settings and home.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@TheSevenPens
TheSevenPens merged commit b8d0c3a into master Sep 2, 2026
3 checks passed
@TheSevenPens
TheSevenPens deleted the fix/nav-spacing branch September 2, 2026 12:28
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