xxshna.ui
V 1.1.0Get started ↗
Components/Navigation

Navigation tree

Show hierarchical destinations with native expandable disclosure sections.

Catalog · 1.1HTML, CSS & optional JSNo runtime dependencies

Live preview

Interactive exampleOpen playground ↗
HTML
<nav class="xsh-tree" aria-label="Product directories">
<details open>
<summary>Workspace</summary>
<div>
<a href="../../components/index.html">Component catalog</a>
<details>
<summary>Documentation</summary>
<div>
<a href="../../guides/installation/index.html">Installation</a>
<a href="../../guides/javascript/index.html">JavaScript API</a>
</div>
</details>
</div>
</details>
</nav>

Installation & markup

Include the local stylesheet and script once on the page, then place the component inside a data-xsh-ui root. The example above works without a build system.

<link rel="stylesheet" href="/dist/xshna-ui.css">
<div data-xsh-ui>
  <!-- Add the HTML example above -->
</div>
<script defer src="/dist/xshna-ui.js"></script>

Component API

Public classes, attributes and hooks used by this example. Keep the xsh- prefix intact.

IdentifierContract
xsh-treeUsed by the example markup and component styles or behavior.
detailsUsed by the example markup and component styles or behavior.
summaryUsed by the example markup and component styles or behavior.

Accessibility & keyboard

Native details toggles with keyboard; nested links remain independently focusable.

Implementation note. For complex ARIA trees with arrow-key navigation use a separately audited implementation.

Interaction contract

Behavioral components use the shared delegated runtime; visual-only primitives rely on semantic HTML and CSS. Runtime controls emit bubbling xsh:* CustomEvents; bind application handlers to those events when server persistence, API data or navigation is required.