Button groups
Join closely related commands into a coherent action group.
Live preview
HTML
<div class="xsh-button-group" role="group" aria-label="Document alignment">
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Aligned left">Left</button>
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Centered">Center</button>
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Aligned right">Right</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-button-group | Used by the example markup and component styles or behavior. |
xsh-button | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Buttons are independently focusable. Group labels should describe the relationship between controls.
Implementation note. Use segmented controls rather than groups for a single persistent selection.
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.