xxshna.ui
V 1.1.0Get started ↗
Components/Navigation

Command menus

Open a keyboard-driven command dialog for common actions.

Catalog · 1.1HTML, CSS & optional JSNo runtime dependencies

Live preview

Interactive exampleOpen playground ↗

Quick actions

HTML
<button class="xsh-button" data-xsh-dialog-open="xsh-command-demo">Open command menu</button>
<dialog id="xsh-command-demo" class="xsh-dialog xsh-command-dialog" aria-label="Quick actions">
<div class="xsh-dialog__header">
<h2 class="xsh-dialog__title">Quick actions</h2>
</div>
<div class="xsh-dialog__body">
<div class="xsh-stack">
<button class="xsh-button xsh-button--secondary" data-xsh-dialog-close data-xsh-toast="info" data-xsh-message="New document selected">+ New document</button>
<button class="xsh-button xsh-button--secondary" data-xsh-dialog-close data-xsh-toast="info" data-xsh-message="Open project selected">⌘ Open project</button>
</div>
</div>
<div class="xsh-dialog__footer">
<button class="xsh-button xsh-button--ghost" data-xsh-dialog-close>Close</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-command-dialogUsed by the example markup and component styles or behavior.
xsh-dialogUsed by the example markup and component styles or behavior.
data-xsh-dialog-openUsed by the example markup and component styles or behavior.

Accessibility & keyboard

Native modal focus containment, Escape, and command buttons are supported.

Implementation note. This is an action-dialog pattern, not a global shortcut registry.

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.