fix(dashboard): stop f2.html header/footer nav bars overlapping page content - #34
Merged
Conversation
…content The top header and mobile bottom nav used the .glass/.glass-strong tint classes (only 3-7% white over the page bg), so scrolled content showed through them. Worse, the tune view's own sticky segmented-tab bar (.tune-stage) was pinned at the same top:0 / z-index:30 as the page header, so the two collided instead of stacking. - add an opaque .app-navbar class for the sticky header and fixed mobile bottom nav - stick .tune-stage below the header's real height (--app-header-h) with a lower z-index so it settles under the header instead of on top of it Fixes #32.
The HACS validation action fails its license check on every PR without a repo-level LICENSE file, unrelated to any particular change.
JakeTheRabbit
marked this pull request as ready for review
July 6, 2026 14:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
www/f2.htmlused the.glass/.glass-strongtint classes (only 3–7% white over the page background), so scrolled content showed through them instead of being blocked..tune-stage) was pinned at the sametop:0/z-index:30as the page header, so on scroll the two stuck to the same spot and rendered on top of each other instead of stacking..app-navbarclass (#0d1117) for the sticky header and fixed mobile bottom nav..tune-stagenow sticks below the header's real height (--app-header-h: 64px) with a lowerz-indexso it settles under the header instead of colliding with it.Fixes #32.
Test plan
www/f2.htmlon desktop — confirm the header stays solid (no content bleeding through) while scrolling the Tune view.🤖 Generated with Claude Code
Generated by Claude Code