layoutstexulinot agent-emittableapp
Top navigation layout
layout-top-nav
Horizontal top navigation with optional mobile menu.
Live examples
Top navigation layout
Top navigation layout
Loading demo…
Props
| Name | Kind | Required | Default | Description |
|---|---|---|---|---|
mountScreen | event | yes | — | Host callback that mounts the stable routed screen node |
nav | object | no | — | NavModel for chrome links |
path | string | no | — | Current hash path |
options | object | no | — | Flat data-only layout knobs |
storageKey | string | no | — | Scope for persisted UI flags |
aside | slot | no | — | Optional context panel |
class | string | no | — | — |
skipLabel | string | no | — | — |
menuLabel | string | no | — | — |
closeLabel | string | no | — | — |
Keyboard
| Key | Action |
|---|---|
a | Primary navigation is a labelled landmark |
Accessibility
- Skip link targets main when chrome is present
- Primary navigation is a labelled landmark
Evidence for layout-top-nav
Latest committed gates for layout-top-nav (as of 2026-10-23). Static snapshot — not live CI.
Behavior
n/ano behavior scenario
No dedicated behavior scenario for this catalog id (a styled or display surface, covered by its unit and axe tests).
Size (gzip)
texuli/layout-top-nav · budget 12.0 KiB
Budget from texuli.budgets.json; re-measure with `pnpm size --filter <entry>`.
Axe
documented
tests/e2e/site-component-pages.spec.tsdocs/quality (a11y-*)
Site component pages axe gate; package-level a11y docs under docs/quality when present.
Browsers
chromiumwebkitmobile
Playwright projects: Desktop Chrome, Desktop Safari, Pixel 7. Firefox is a known gap on this host.
When to use
Use when
- Product shells with a top bar
Don’t use when
Prefer another component
- Dense multi-section sidebars