Skip to content
Xshna.cssv1.0.0-beta.2
PlaygroundUtilities
DOCUMENTATION / ENGINEERING
XSHNA.CSS 3.0 / PRODUCTION HANDBOOK

Enterprise component contracts

Combobox, paged grid, wizard and adaptive patterns. Practical engineering and integration guidance for serious commercial applications.

V1 BETA / DOCUMENTEDLive variants · API · Accessibility · Responsive guidance

Combobox

The optional runtime enhances a combobox consisting of [data-xsh-combobox], a text input with role=combobox and a [role=listbox] with child [role=option] elements. Arrow keys select the active option, Enter commits and Escape dismisses. Items must have meaningful text or data-xsh-value. This is a locally filtered list, not server-backed async autocomplete.

Combobox example

<div class="xsh-combobox" data-xsh-combobox>
 <label for="xsh-city">City</label>
 <input id="xsh-city" class="xsh-input" role="combobox" autocomplete="off" aria-label="City">
 <ul class="xsh-combobox-list" id="xsh-cities" role="listbox" hidden>
  <li id="xsh-city-raipur" role="option" aria-selected="false">Raipur</li>
  <li id="xsh-city-delhi" role="option" aria-selected="false">Delhi</li>
 </ul>
</div>

Paged grid

Use table[data-xsh-paginate="10"] with an ID, plus a pagination container data-xsh-grid-for pointing at the ID or a table with data-xsh-pagination targeting a container. Use an input with data-xsh-grid-search="#xsh-table-id" to search client-side. Paging operates on HTML table rows; it is not virtualization. For thousands of rows or confidential data, use backend pagination and authorization.

Grid example

<div class="xsh-adapt-table">
 <table id="xsh-orders" class="xsh-data-grid" data-xsh-paginate="5" data-xsh-pagination="#xsh-order-pages">
  <thead><tr><th scope="col">Order</th><th scope="col">Amount</th></tr></thead>
  <tbody><tr><td>INV-001</td><td>₹1,200</td></tr></tbody>
 </table>
</div>
<div id="xsh-order-pages" class="xsh-data-grid-foot"></div>

Wizard forms

An element with data-xsh-wizard contains panels with data-xsh-step. Buttons use data-xsh-next and data-xsh-prev. Before moving forward the runtime checks native form constraints in the current panel. Application code must separately enforce server-side validation, authorization and transaction integrity.

Lifecycle

Xshna.init(document) attaches document-level handlers, Xshna.refresh(root) refreshes selected enhanced components after adding DOM, and Xshna.destroy(document) releases handlers. Do not mix multiple JS versions or import both the full bundle and individual modules simultaneously.

Release status: Use the acceptance checklist before representing any feature as independently certified or accessible in all browsers. Tests delivered with the package are evidence of only the checks actually performed.
REFERENCE CONTRACT

Files, tokens and configuration

SurfaceSource of truthWhat to check
dist/xshna.min.cssCompiled frameworkStyling and responsive behavior
dist/xshna.min.jsOptional interactionsLifecycle, event handling and teardown
src/css/Readable sourcePublic class names and token definitions
src/contracts/Published component contracts where availableState, configuration and behavioral support
ENGINEERING AND INTEGRATION

Implementation details

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.

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.

ACCEPTANCE CHECKLIST

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.