2 Commits

Author	SHA1	Message	Date
Joseph Doherty	f1efe6e081	fix(theme): 0.3.1 — interactive-render nav backstop (issue #6) ... Under an interactive Blazor render mode the runtime replaces the prerendered <details> after DOMContentLoaded, so nav-state.js (wired on load, re-run only on 'enhancedload') never wires the live rail — no aria sync, no persistence, no active-reveal — and native <details> content-hiding is unreliable, leaving a collapsed section's items visible. 0.3.1: - nav-state.js: add a MutationObserver backstop that re-runs apply() when details.rail-section nodes are (re)inserted; idempotent via the per-element init guard, loop-safe (childList-only + active-reveal's !open guard). - layout.css: explicit .rail-section:not([open]) > .rail-section-body{display:none} so visual collapse works across all render modes. - themeissues.md: document issue #6; Directory.Build.props 0.3.0 -> 0.3.1. 48 bUnit tests green.	2026-06-05 07:18:30 -04:00
Joseph Doherty	0e41e7c2e4	fix(theme): resolve nav/login kit issues + bump 0.2.1 -> 0.3.0 ... Addresses ZB.MOM.WW.Theme/themeissues.md: - #1 NavRailSection <summary> renders aria-expanded (SSR from Expanded), kept in sync by nav-state.js on restore + toggle. - #2 nav-state.js auto-expands the section holding a.rail-link.active (transient via data-zbnav-transient — does not overwrite saved state). - #3 nav-state.js re-applies on Blazor 'enhancedload' (idempotent via per-element init guard). - #5 LoginCard wraps product in span.login-product + optional Heading override param. - #4 documented as an accepted client-only-persistence tradeoff (no code change). +4 bUnit tests (48 total, all green).	2026-06-05 04:42:24 -04:00