Popovers
Reveal contextual nonmodal information on demand.
Live preview
Billing cycle
Invoices are generated on the first of each month.
HTML
<div class="xsh-popover-shell" data-xsh-popover>
<button class="xsh-button xsh-button--secondary" type="button" aria-expanded="false" data-xsh-popover-trigger>Billing details ▾</button>
<div class="xsh-popover" hidden>
<strong>Billing cycle</strong>
<p>Invoices are generated on the first of each month.</p>
<button class="xsh-button xsh-button--sm" type="button" data-xsh-popover-close>Got it</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-popover-shell | Used by the example markup and component styles or behavior. |
xsh-popover | Used by the example markup and component styles or behavior. |
data-xsh-popover-trigger | Used by the example markup and component styles or behavior. |
data-xsh-popover-close | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
The trigger toggles with Enter/Space; Escape dismisses and restores focus.
Implementation note. Use a native dialog for confirmation, not a popover.
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.