Skip to content
Xshna.cssv1.0.0-beta.2
PlaygroundUtilities
DOCUMENTATION / FOUNDATIONS
Foundations / Component reference

Motion

Coordinated motion modes with automatic reduced-motion handling.

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

Overview

Set data-xsh-motion=none|subtle|expressive, use xsh-transition-all and xsh-duration-300 utilities.

Live example

Interactive · Real framework

Example markup

<button class="xsh-btn xsh-btn-primary xsh-transition-all xsh-hover-scale-105">Hover carefully</button>

Production guidance

Reduced-motion preferences override decorative motion. Avoid animations that hide critical content.

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.

EXACT NAMES FROM THE SHIPPED STYLESHEETS

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.

ClassPurposeDelivery
.xsh-animate-fadeComposable modifier / structure classCSS-only
.xsh-animate-riseComposable modifier / structure classCSS-only
.xsh-animate-scaleComposable modifier / structure classCSS-only
ENGINEERING AND INTEGRATION

Implementation details

Semantic structure

Animation must never be necessary to access information.

Compose existing xsh- classes on the appropriate HTML element. Keep content order meaningful when CSS is disabled.

Interactive behavior

Use prefers-reduced-motion to disable or simplify nonessential movement.

Load xshna.min.js only if the documented interaction needs it. Your application remains responsible for data, persistence and business rules.

Responsive and localization

Avoid continuous expensive blur/filter effects on dense interfaces.

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.