Repository navigation
Fix responsive header layout after adding Editor - #25
Merged
Merged
Conversation
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
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.
Adding “Try the editor” made the fixed-height header wrap and clip at common desktop widths; wide-screen spacing also broke it again at 2,560px. This shortens the navigation label to “Editor”, keeps desktop links on one line with consistent spacing, and uses the existing compact menu below 1,280px. The expanded compact menu scrolls on short screens. All ten destinations, search and the client version badge are preserved.
Adds Chromium, Firefox and WebKit CI checks against the actual built-site artifact: 15 widths on two pages, normal/fallback fonts, no clipping or overlapping controls, exact link origins, keyboard search/Editor/Donate activation and menu resizing. The test build uses a local base URL and checks stylesheet identity so it cannot accidentally test production CSS.
Validation:
Production deployment remains the existing main-branch workflow. No editor bundle or demo/download bytes change.