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.
Components / Component reference
Popovers and tooltips
Native HTML popovers and CSS-only tooltips for short annotations.
LIVE COMPONENT REFERENCE
Popover and tooltip
Tooltips add brief, noninteractive descriptions. Popovers may contain more detailed content; native popover attributes provide baseline dismissal.
Actual Xshna CSSResponsive preview
HTML · COPY AND USE
<div class="xsh-ref-flex"><button class="xsh-btn xsh-btn-primary" popovertarget="xsh-premium-popover" type="button">Open detail</button><div class="xsh-popover" popover id="xsh-premium-popover"><strong>Project details</strong><p>This interface uses the native popover API.</p></div><button type="button" class="xsh-btn xsh-btn-outline xsh-tooltip" data-xsh-tooltip="Helpful additional context">Focus or hover</button></div>Overview
Use popover attribute with a button popovertarget, or xsh-tooltip data-xsh-tooltip on a keyboard-focusable element.
Live example
Interactive · Real frameworkPopover detail
Useful contextual information.
Example markup
<div class="xsh-flex xsh-items-center xsh-gap-4"><button class="xsh-btn xsh-btn-secondary" popovertarget="xsh-popover-demo">Open popover</button><div class="xsh-popover" popover id="xsh-popover-demo"><strong>Popover detail</strong><p>Useful contextual information.</p></div><button class="xsh-btn xsh-btn-ghost xsh-tooltip" data-xsh-tooltip="A short explanation">Tooltip trigger</button></div>Production guidance
Tooltips should never hold essential interactive content. Native popover support depends on the browser.
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.
Build with confidenceOpen interactive design playground →
Complete selector inventory
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-popover | Core component | CSS-only |
Implementation details
Interactive behavior
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.
Responsive and localization
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.
Theme and customization
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.
What to verify before shipping
- Confirm every documented class used by the feature exists in the release CSS.
- Navigate controls using Tab, Shift+Tab, Enter, Space and Escape where appropriate.
- Test with reduced motion, high contrast, 200% text zoom and a narrow mobile viewport.
- Verify disabled, loading, empty, error and long-content states where relevant.
- Check actual application behavior independently of the preview: these examples use illustrative data.