InputsComponentBeta

Text Field.

Room for a thought to take shape.

TextField is the styled input; Field owns label, description and validation relationships. Native editing, autocomplete, refs and value callbacks remain with Base UI. Use Field.Control for the lower-level input contract.

Make it yours

Preparing the example…

PROPERTIES6

Composition

Anatomy

TextField is the styled input; Field owns label, description and validation relationships. Native editing, autocomplete, refs and value callbacks remain with Base UI. Use Field.Control for the lower-level input contract.

Component structure
Field.Root (invalid, disabled)
├── Field.Label
├── TextField (size, variant, radius, material)
├── Field.Description
└── Field.Error

A place to start

Usage

Import the stylesheet once at your application root. This complete example reflects the properties selected above.

Loading example…

Details that make a difference

Examples & states

Sizes

Compare the three Dixy shirt sizes side by side.

Example loads as it comes into view.

Loading source…

Visual treatments

Emphasis changes presentation while the primitive keeps behavior.

Example loads as it comes into view.

Loading source…

Corner radii

Contextual rounding applies to the control or surface; large panels stay readable.

Example loads as it comes into view.

Loading source…

Materials

Optional static finishes use the same public component. Import materials.css in your application.

Example loads as it comes into view.

Loading source…

The finer details

API reference

Generated from Dixy’s local TypeScript interfaces. Native and Base UI Input props are forwarded; this table covers the options Dixy adds.

TextField

PropType / descriptionDefault
size"sm" | "md" | "lg"

The height and type size of the control.

md
variant"soft" | "outline"

The visual surface treatment.

outline
radius"none" | "sm" | "md" | "lg" | "full"

Input rounding.

Theme.radius
material"matte" | "glossy" | "soft" | "metal" | "paper"

Optional static finish; import materials.css.

Theme.material
Explore the full Base UI API

Built from the same foundations

Styling tokens

Change Theme settings above to compare appearance, accent, neutral, radius, spacing density, motion and direction. Override component aliases on a Theme root so custom properties follow portaled content too. The wrapper merges className, style, refs and render composition with its owning primitive.

TokenPurpose
--dixy-input-borderThe component-specific starting point.
--dixy-font-label-mdControl label font and line height; body roles remain readable in text inputs.
--dixy-color-background-selectedSelected surfaces use semantic color across appearances.
--dixy-color-border-focusFocus indication remains visible independently of shadows.
--dixy-spacing-inset-smDensity-aware component padding.
--dixy-motion-transition-feedbackShort state feedback, reduced by the inherited motion setting.
Explore theme customization

Consider everyone

Accessibility

A placeholder is not a label. Field.Label and Field.Description establish accessible relationships. Invalid fields should explain how to recover through Field.Error. Keep native autocomplete and form semantics.

TabMove focus into or out of the input.
Arrow keysMove the text caret using native input behavior.

Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.

THE THINKING BEHIND IT

Build it. Then understand it.

Field and Input share Base UI context. The label and description are linked without hand-written IDs. Controlled values need a matching onValueChange callback. Visual settings follow Dixy shirt sizes, contextual radii and semantic tokens where applicable. Static finishes are optional, and reduced motion is immediate. Base UI keeps refs, state, events, keyboard and presence; this implementation pass does not establish WCAG conformance.

A token to follow--dixy-input-border

Nothing up our sleeves

Source
UP NEXTDialog