Form action bars
Keep save, cancel, and discard commands consistently positioned.
Live preview
Unsaved changes
HTML
<div class="xsh-form-actions">
<span class="xsh-help">Unsaved changes</span>
<button class="xsh-button xsh-button--secondary" data-xsh-toast="info" data-xsh-message="Nothing was changed in this demo.">Cancel</button>
<button class="xsh-button" data-xsh-toast="success" data-xsh-message="Local example only; connect to your endpoint.">Save changes</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-form-actions | 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 use native Enter/Space activation; sample actions report locally.
Implementation note. Never claim to save to a server without an application endpoint.
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.