Navigation first-paint fix
Scope
The expanded no-JS navigation previously remained in normal layout until
DOMContentLoaded added nav-ready. On a 412px viewport this changed the header
from 940px to108px and moved the hero upward832px. The successfully loaded head
script now marks navigation capability before body paint. CSS reserves the
compact layout without waiting for initialization. Disabled JavaScript and a
blocked script download retain expanded accessible links. Initialization errors
remove the capability marker and inert attributes to restore that fallback.
Tradeoff: this small script is now parser-blocking. A slow script request can delay first paint, but a failed request does not leave navigation inaccessible. An initialization error may still cause a layout jump when restoring fallback; accessibility is deliberately prioritized in that exceptional path.
The Sabre portrait also now reserves its existing350×525px,2:3 box before decode. It remains responsive at smaller widths. No image format/content was changed.
Verification (2026-11-15)
-Full Node suite:25/26 passed. The sole sitemap failure is reproduced on unchanged baseline.
-Three bootstrap regressions,13 Sabre reel tests and all navigation tests passed.
-JavaScript syntax and git diff --check passed; navigation SCSS compiled with Sass.
-Isolated Chrome checks passed for drawer open/close, Escape/focus restoration,
Tab wrap, keyboard dropdown operation, repeated toggles, background inert
restoration, desktop dropdown, and disabled/blocked/failing JavaScript.
-Disabled/blocked initialization preserved15 accessible links. Successful412px
initialization held the header at108px with no observed layout shifts.
-Browser tests used the live rendered HTML with only local source changes
substituted in a disposable browser. They are not a deployment.
Controlled Lighthouse13.6.0 mobile A/B (three alternating runs per version; HTML/nav assets supplied locally, other resources fetched normally):
| Version | Scores | LCP seconds | CLS |
|---|---|---|---|
| Baseline | 69,85,58 | 8.37,4.00,4.18 | 0,0,.869 |
| Fixed | 92,83,92 | 3.10,3.95,3.14 | 0,0,0 |
Median score69→92; median LCP4.18→3.14 seconds. These controlled measurements are not production PSI/CrUX data or a promise of identical deployed results.
Remaining validation
Full Jekyll build passed. Initial native Nokogiri compilation failed, then was resolved for validation using official precompiled ARM gems at the same locked versions. Only a temporary copy of the lockfile gained ARM platform variants; repository Gemfile and lockfile remain unchanged.
All26 tests ran:25 passed. The remaining sitemap test expects /learn.html while that page declares canonical /learn. The identical failure reproduced in a fresh unchanged baseline checkout (public-journey suite9/10). It is unrelated to this navigation fix and was not changed. Full-suite testing also prompted an idempotence guard so repeated navigation setup cannot duplicate click handlers.
No push, merge or deployment performed. Recheck production Lighthouse after an authorized deployment.