Skip to content

feat(ui): Import/Export nav entries; the sidebar rail expands on hover - #440

Open
angela-helios wants to merge 6 commits into
mainfrom
feat/438-nav-hover-rail
Open

feat(ui): Import/Export nav entries; the sidebar rail expands on hover#440
angela-helios wants to merge 6 commits into
mainfrom
feat/438-nav-hover-rail

Conversation

@angela-helios

@angela-helios angela-helios commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Closes #438
Closes #442

Two sidebar updates from the current designs:

Batch & Data entries. An Import entry joins the section (new mirrored icon), and Bulk Export becomes Export — placeholders like their siblings until those pages exist. Three locales updated.

Hover-expanding rail. The explicit collapse toggle is gone, together with nav.js, its data-nav state machine, and the persisted expanded/collapsed preference (the /_user/settings nav key is simply no longer read). The sidebar is now a fixed icon rail that expands as an overlay while hovered — or keyboard-focused, so it stays keyboard-accessible — and the content column never reflows. The narrow-viewport media block and the has-nav-panel grid variants collapsed into the one base state, since the rail is now the resting state everywhere. Labels stay in the accessibility tree while the rail is closed (same visually-hidden pattern as before).

Screenshots

Resting rail:

resting rail

Hovered — expands as an overlay, with the new Import/Export entries:

hovered rail

Resources page (the three-column has-nav-panel layout keeps its own columns):

resources with rail

Tests

  • router_http: the page ships no toggle and no nav.js, and lists Import/Export.
  • e2e chrome.spec.ts rewritten: rail width at rest, expands on hover and on keyboard focus, collapses on leave, content column doesn't move, no toggle in the DOM, and the Batch & Data section lists Import/Export/SQL-on-FHIR. Full suite green locally (57 passed), a11y and no-cdn included.

Update: the e2e Recent failure turned out to be a pre-existing server bug this PR uncovered (#442): GET /_user/settings hands out ETag: "0" for the never-written document, but check_if_match rejected that same validator on conditional writes, so a fresh user's read-then-conditional-write 412'd forever — previously masked by nav.js's unconditional first PATCH. The fix (one function in handlers/user_settings.rs + two regression tests, 25/25 in user_settings) is folded into this PR; If-Match: * keeps requiring an existing document, and all four storage backends already treated expected version 0 as insert-if-absent.

The Batch & Data section catches up with the designs: an Import entry
joins, and Bulk Export becomes Export (placeholders like their siblings
until those pages exist).

The explicit collapse toggle is gone with its nav.js state machine and
the persisted expanded/collapsed preference. The sidebar is now a fixed
icon rail that expands as an overlay while hovered or keyboard-focused,
so the content column never reflows. The narrow-viewport media block and
the has-nav-panel grid variants collapse into the one base state.

Closes #438
position: fixed removes the sidebar from the grid flow, so the pane was
auto-filling the rail column. The pane and the optional nav panel now name
their columns.
@codecov

codecov Bot commented Jul 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Linux headless registers the initial pointer at (0,0) — over the rail — so
pages opened with the sidebar expanded, overlaying the left content edge;
any click landing under the overlay kept it hovered and intercepted
forever. The page fixture now parks the pointer in the empty topbar after
every goto, and the nojs nav-link tests hover the rail and wait for the
expansion to settle before clicking, since item positions shift between
the two states.
GET serves the empty settings document as a real representation ({} with
ETag "0"), but check_if_match mapped version 0 to 'no representation',
so the validator the GET handed out could never satisfy a conditional
write: a fresh user's read-then-conditional-write 412'd forever. Concrete
tag lists now evaluate against the version number including 0; If-Match: *
keeps requiring an actually stored document. The storage layer already
treated an expected version 0 as insert-if-absent on all four backends.

Closes #442
The 250px threshold accepted a mid-transition width, so the link could
still be moving when the click landed.
@angela-helios

Copy link
Copy Markdown
Contributor Author

CI status: everything is green except the one e2e failure — queries.spec.ts › a run is recorded under the Recent disclosure — which is the pre-existing server bug #442 that this PR merely uncovers (removing nav.js removed the unconditional PATCH that used to paper over it). #443 fixes it and is fully green; once it merges, re-running this PR's suite goes green. Suggested order: #443 first, then this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants