Visible process name.
Primitive contract
Progress
Styles native progress semantics and visible labels without adding runtime behavior or implying completion from motion.
Visible determinate or pending progress · @sanchika/primitivesPurpose and semantics
Styles native progress semantics and visible labels without adding runtime behavior or implying completion from motion.
Recommended semantic: Prefer native progress with a visible label and value; consumers provide an equivalent semantic for indeterminate context when needed.
Anatomy
Determinate value semantics.
Visible numeric or state wording.
Finite variants and important states
- Variant · state
- determinate, indeterminate, complete, error
- Required states
- determinate, indeterminate, complete, error
- Class hooks
.sk-progress · .sk-progress-indeterminate · .sk-progress-complete · .sk-progress-error · .sk-progress__header · .sk-progress__value
Composed synthetic exemplar
Rendered state matrix
Progress: 4 required states
Each specimen starts from the package-owned example and contract state inventory. Simulated pointer and focus frames are labelled; consumers still verify real interaction in context.
Checking sources3 of 5
Checking sources3 of 5
Checking sources3 of 5
Checking sources3 of 5
Accessibility and consumer responsibility
- Progress itself is not interactive.
- Associate visible label
- Keep value and text consistent
- Do not announce cosmetic animation
- Update native values
- Choose truthful pending/error wording
- Do not claim completion prematurely
- Label and value wrap above the full-width meter
No override is required.
- Native progress and visible text remain distinguishable
Compact API reference
- Package
@sanchika/primitives- CSS
@sanchika/primitives/styles.css- Contract
primitiveSpecs.find((contract) => contract.name === "Progress")- Primary class
.sk-progress