xxshna.ui
V 1.1.0Get started ↗
Components/Data display

Tags

Label selected items, with optional safe removal controls.

Catalog · 1.1HTML, CSS & optional JSNo runtime dependencies

Live preview

Interactive exampleOpen playground ↗
Design systems Frontend Accessibility
HTML
<div class="xsh-row">
<span class="xsh-tag">Design systems <button type="button" data-xsh-tag-remove aria-label="Remove Design systems tag">×</button>
</span>
<span class="xsh-tag">Frontend <button type="button" data-xsh-tag-remove aria-label="Remove Frontend tag">×</button>
</span>
<span class="xsh-tag">Accessibility <button type="button" data-xsh-tag-remove aria-label="Remove Accessibility tag">×</button>
</span>
</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.

IdentifierContract
xsh-tagUsed by the example markup and component styles or behavior.
data-xsh-tag-removeUsed by the example markup and component styles or behavior.
xsh:tag-removeUsed by the example markup and component styles or behavior.

Accessibility & keyboard

Removal is a native button with a complete accessible label. Keep tag text visible.

Implementation note. Deleting a visual tag does not persist changes; listen for xsh:tag-remove to update application state.

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.