Buttons
Provide a clear, consistent action hierarchy across application surfaces.
Live preview
HTML
<div class="xsh-row">
<button class="xsh-button" data-xsh-toast="success" data-xsh-title="Changes saved" data-xsh-message="Your workspace has been updated.">Primary action ↗</button>
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Secondary action activated.">Secondary</button>
<button class="xsh-button xsh-button--ghost" data-xsh-toast="info" data-xsh-message="Ghost action activated.">Ghost</button>
<button class="xsh-button xsh-button--danger" data-xsh-toast="danger" data-xsh-message="Deletion requires confirmation in your application.">Destructive</button>
<button class="xsh-button" disabled>Disabled</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 | Used by the example markup and component styles or behavior. |
xsh-button--secondary | Used by the example markup and component styles or behavior. |
xsh-button--ghost | Used by the example markup and component styles or behavior. |
xsh-button--soft | Used by the example markup and component styles or behavior. |
xsh-button--danger | Used by the example markup and component styles or behavior. |
xsh-button--sm | Used by the example markup and component styles or behavior. |
xsh-button--lg | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Use native button elements. Enter and Space activate actions; disabled buttons are removed from the tab order.
Implementation note. Use the primary style once per decision area. Never style navigation as a destructive action.
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.