A localized native range input with visible output, controlled value, orientation metadata, and form reset.
Since
1.0.0-next.0
Owner
Brand Core
Export
PRIVATE_BETA_PACKAGE_COORDINATE_REDACTED/Slider
Release
Documentation version
Deterministic fixture · default state
Component studio
Preview controls could not be applied. The static default fixture remains available.
§01
Contract
Semantics first
Anatomy
Uses input type=range with a linked label and output; native slider semantics expose min, max, step, and value.
Consumer classes, styles, and data attributes may extend the surface, but required roles, IDs, relationships, and handlers remain owned by the component.
Keyboard
Tab focuses the slider.
Arrow keys adjust by step; Page Up/Down and Home/End follow browser range behavior.
Direction and vertical presentation must preserve the platform value model.
§02
Public surface
API & styling
Props
id
Explicit IDs override stable generated IDs.
class / style
Consumer additions compose with required styles.
ref
Element or callback where focus control is expected.
children
Typed content; raw HTML strings are never rendered.
Slots & events
children
Primary content slot.
onChange
Typed value plus a small reason object when state changes.
import Slider from 'PRIVATE_BETA_PACKAGE_COORDINATE_REDACTED/Slider';
<Slider>Frauthy content</Slider>
Astrostatic
---
import Slider from 'PRIVATE_BETA_PACKAGE_COORDINATE_REDACTED/Slider';
---
<Slider>Frauthy content</Slider>
§04
Verification
Evidence record
Scheduled
Automated
Batch D form tests cover controlled/default values, localized output and aria-valuetext, input/change reasons, reset, orientation, constraints, and errors.
Target
Brand 1.0.0-next.0 matrix
Last verified
Pending integrated G2 run
Required
Assistive technology
Pending VoiceOver/Safari and NVDA/Firefox value/unit announcement plus vertical-orientation verification.
Desktop
VoiceOver/Safari · NVDA/Firefox
Touch
Required for touch-centric behavior
Open
Known issues
Native vertical range rendering is not uniform across browsers and depends on the Brand CSS implementation.
Slider is single-thumb; ranges are out of scope.
§05
Editorial guidance
Do / don’t
Do
Use when approximate adjustment is acceptable and show the formatted value.
Don’t
Do not use Slider when users must enter or compare an exact value without a paired numeric control.
There is no stable predecessor for this explicit compiled subpath. The v1 compatibility layer remains tested separately; visual and API diffs begin with the next prerelease.