Action toolbars
Group application-level commands with concise labels and visual hierarchy.
Live preview
HTML
<div class="xsh-action-toolbar" role="toolbar" aria-label="Document actions">
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Edit requested">Edit</button>
<button class="xsh-button xsh-button--secondary" data-xsh-copy="xsh-toolbar-copy">Copy ID</button>
<code id="xsh-toolbar-copy" class="xsh-code">WK-1024</code>
<span class="xsh-action-toolbar__divider">
</span>
<button class="xsh-button xsh-button--danger" data-xsh-toast="warning" data-xsh-message="Requires an application confirmation step">Delete</button>
</div>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.
| Identifier | Contract |
|---|---|
xsh-action-toolbar | Used by the example markup and component styles or behavior. |
data-xsh-copy | Used by the example markup and component styles or behavior. |
role=toolbar | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Tab visits each native button; Copy uses Clipboard API with fallback.
Implementation note. Toolbar roles are useful when grouping meaningful related commands; do not suppress native focus.
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.