Semantic structure
Use the documented Xshna classes with semantic HTML rather than replacing native elements unnecessarily.
Compose existing xsh- classes on the appropriate HTML element. Keep content order meaningful when CSS is disabled.
Native progress bars, meters, spinners, and skeleton placeholders.
Use indeterminate loading for unknown durations. When you know a percentage, expose a real progress value.
<div class="xsh-ref-flex"><progress class="xsh-progress" max="100" value="72">72%</progress><span class="xsh-spinner" aria-label="Loading" role="status"></span><div class="xsh-skeleton" style="width:125px;height:15px" aria-hidden="true"></div><div class="xsh-skeleton xsh-skeleton-circle" style="width:38px;height:38px" aria-hidden="true"></div></div>Prefer native progress and meter elements with descriptive text. Use xsh-skeleton for placeholder geometry and xsh-spinner for busy states.
<div class="xsh-stack"><label for="xsh-progress-demo" class="xsh-label">Upload progress: 62%</label><progress class="xsh-progress" id="xsh-progress-demo" max="100" value="62">62%</progress><div class="xsh-flex xsh-items-center xsh-gap-3"><span class="xsh-spinner" aria-hidden="true"></span><span>Preparing preview...</span></div><div class="xsh-skeleton xsh-skeleton-line" aria-hidden="true"></div><div class="xsh-skeleton xsh-skeleton-line xsh-w-1-2" aria-hidden="true"></div></div>Customize this component through --xsh-* CSS tokens, data-xsh-* configuration attributes and documented xsh-* utilities. Use the optional JavaScript distribution only when an interactive behavior is needed.
These selectors exist in the current distribution. An entry in this table does not imply that arbitrary modifier combinations are meaningful; use the examples above for the intended composition.
| Class | Purpose | Delivery |
|---|---|---|
.xsh-progress | Core component | CSS-only |
.xsh-progress-steps | Composable modifier / structure class | CSS-only |
Use the documented Xshna classes with semantic HTML rather than replacing native elements unnecessarily.
Compose existing xsh- classes on the appropriate HTML element. Keep content order meaningful when CSS is disabled.
Verify focus order, disabled behavior and descriptive labels for interactive patterns.
Load xshna.min.js only if the documented interaction needs it. Your application remains responsible for data, persistence and business rules.
Test narrow containers, long translations and user-defined text sizes.
Test 320px-wide viewports, container-constrained instances, keyboard zoom, longer translations and right-to-left text where relevant.
Use --xsh-* CSS variables for theme values and data-xsh-design / data-xsh-density on the xsh-app root.
Prefer design tokens over hard-coded overrides so components remain coherent across personalities.