xxshna.ui
V 1.1.0Get started ↗
Components/Overlays

Confirmation dialogs

Require an explicit confirmation before destructive or irreversible changes.

Catalog · 1.1HTML, CSS & optional JSNo runtime dependencies

Live preview

Interactive exampleOpen playground ↗

Remove environment?

This is a UI-only confirmation example. No environment will be deleted.
HTML
<button class="xsh-button xsh-button--danger" data-xsh-dialog-open="xsh-confirm">Remove environment</button>
<dialog id="xsh-confirm" class="xsh-dialog" aria-labelledby="xsh-confirm-title" aria-describedby="xsh-confirm-desc">
<div class="xsh-dialog__header">
<h2 class="xsh-dialog__title" id="xsh-confirm-title">Remove environment?</h2>
</div>
<div class="xsh-dialog__body" id="xsh-confirm-desc">This is a UI-only confirmation example. No environment will be deleted.</div>
<div class="xsh-dialog__footer">
<button class="xsh-button xsh-button--secondary" data-xsh-dialog-close>Cancel</button>
<button class="xsh-button xsh-button--danger" data-xsh-dialog-close data-xsh-toast="warning" data-xsh-message="Confirmed in the example only.">Confirm</button>
</div>
</dialog>

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.

IdentifierContract
xsh-dialogUsed by the example markup and component styles or behavior.
data-xsh-dialog-openUsed by the example markup and component styles or behavior.
aria-describedbyUsed by the example markup and component styles or behavior.

Accessibility & keyboard

Native modal keyboard trapping and Escape-to-cancel work.

Implementation note. Only execute irreversible operations after server authorization and confirmation.

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.