Skip to content

fix(ui): close 641-767px rail/hamburger breakpoint gap - #956

Merged
nesquena-hermes merged 1 commit into
masterfrom
fix/rail-layout-polish
Apr 24, 2026
Merged

fix(ui): close 641-767px rail/hamburger breakpoint gap#956
nesquena-hermes merged 1 commit into
masterfrom
fix/rail-layout-polish

Conversation

@nesquena-hermes

Copy link
Copy Markdown
Collaborator

Follow-on polish from #899 (three-column layout).

Change

At 641–767px the layout was in an awkward gap: the hamburger was hidden (only shows at ≤640px) and the rail was also hidden (only shows at ≥768px). The sidebar stayed as a persistent panel with sidebar-nav tabs visible, so navigation still worked — but the rail was absent for no good reason.

Fix: move the rail breakpoint from min-width:768px to min-width:641px. The mobile slide-in behavior (sidebar position:fixed, hamburger toggle, overlay scrim) stays at ≤640px only — no change to mobile UX.

Before / after

Viewport Before After
≤640px Mobile (hamburger + slide-in) Unchanged
641–767px No rail, no hamburger — sidebar-nav only Rail visible + sidebar-nav
≥768px Rail visible, sidebar-nav hidden Unchanged

Testing

  • CSS change only (1 line)
  • JS syntax: clean
  • 35 regression tests pass (settings navigation + sprint34)

At 641-767px the sidebar was in a no-mans-land: hamburger hidden (<=640 only)
and rail also hidden (>=768 only). Users could still navigate via the sidebar-nav
tabs inside the sidebar, but the rail was absent unnecessarily.

Changing the rail breakpoint from min-width:768px to min-width:641px closes the
gap. The sidebar slide-in behavior (position:fixed, hamburger toggle) stays at
<=640px only, so the mobile UX is unchanged. At 641-767px the rail now appears
alongside the persistent sidebar.
@nesquena-hermes
nesquena-hermes merged commit 533edbc into master Apr 24, 2026
3 checks passed
nesquena-hermes added a commit that referenced this pull request Apr 24, 2026
Co-authored-by: nesquena-hermes <nesquena-hermes@users.noreply.github.com>
JKJameson pushed a commit to JKJameson/hermes-webui that referenced this pull request Apr 25, 2026
At 641-767px the sidebar was in a no-mans-land: hamburger hidden (<=640 only)
and rail also hidden (>=768 only). Users could still navigate via the sidebar-nav
tabs inside the sidebar, but the rail was absent unnecessarily.

Changing the rail breakpoint from min-width:768px to min-width:641px closes the
gap. The sidebar slide-in behavior (position:fixed, hamburger toggle) stays at
<=640px only, so the mobile UX is unchanged. At 641-767px the rail now appears
alongside the persistent sidebar.

Co-authored-by: nesquena-hermes <nesquena-hermes@users.noreply.github.com>
JKJameson pushed a commit to JKJameson/hermes-webui that referenced this pull request Apr 25, 2026
Co-authored-by: nesquena-hermes <nesquena-hermes@users.noreply.github.com>
@nesquena-hermes
nesquena-hermes deleted the fix/rail-layout-polish branch April 28, 2026 00:00
SysAdminDoc pushed a commit to SysAdminDoc/hermes-webui that referenced this pull request Jun 26, 2026
At 641-767px the sidebar was in a no-mans-land: hamburger hidden (<=640 only)
and rail also hidden (>=768 only). Users could still navigate via the sidebar-nav
tabs inside the sidebar, but the rail was absent unnecessarily.

Changing the rail breakpoint from min-width:768px to min-width:641px closes the
gap. The sidebar slide-in behavior (position:fixed, hamburger toggle) stays at
<=640px only, so the mobile UX is unchanged. At 641-767px the rail now appears
alongside the persistent sidebar.

Co-authored-by: nesquena-hermes <nesquena-hermes@users.noreply.github.com>
SysAdminDoc pushed a commit to SysAdminDoc/hermes-webui that referenced this pull request Jun 26, 2026
Co-authored-by: nesquena-hermes <nesquena-hermes@users.noreply.github.com>
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