Input groups
Place contextual prefixes and actions next to an input while preserving native semantics.
Live preview
HTML
<div class="xsh-stack" style="width:100%;max-width:480px">
<label class="xsh-label" for="xsh-demo-domain">Project domain</label>
<div class="xsh-input-group">
<span class="xsh-input-prefix" aria-hidden="true">@</span>
<input class="xsh-input" id="xsh-demo-domain" placeholder="your-project">
<button class="xsh-button xsh-button--secondary" type="button" data-xsh-toast="info" data-xsh-message="Domain availability must be checked against your own backend.">Check</button>
</div>
</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-input-group | Used by the example markup and component styles or behavior. |
xsh-input-prefix | Used by the example markup and component styles or behavior. |
xsh-input | Used by the example markup and component styles or behavior. |
xsh-button | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Maintain an accessible label. Adjacent buttons remain keyboard focusable and have descriptive text.
Implementation note. The library supplies layout only; server-side domain validation belongs to your application.
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.