Stable in React
Radio Group
Provides shared state to a series of radio buttons: one value, one name for the form, and arrow-key movement between them.
Install#
One package per framework. Radio Group's parts come from it; the anatomy tab at the top shows how they nest.
bun add @▢▢▢▢/reactOne part. The example uses one of them; the data does not say which are required.
RadioGroupProvides shared state to a series of radio buttons.
Examples#
The demo at the top is the one example this component has so far.
Styling and accessibility#
The parts ship no styles. Style their states with these attributes; the CSS tab at the top has a sheet. The same CSS works in all five frameworks.
[data-disabled]Present when the radio group is disabled. On RadioGroup.
Keyboard
- ArrowDownArrowUpArrowLeftArrowRightMoves to the next or previous radio and selects it On RadioGroup.
- SpaceSelects the focused radio On RadioGroup.
- EnterDoes not select, as with native radios On RadioGroup.
- TabLeaves the group in one step On RadioGroup.
Set for you
the radios are announced as one setRadioGrouprole="radiogroup"the set is read with its questionRadioGrouparia-labelledbyto the Field label or the Fieldset legendthe group's constraints are announcedRadioGrouparia-disabled,aria-readonly,aria-requiredfromdisabled,readOnlyandrequired
API reference#
9 props across 1 parts, in React syntax, and className, style, render once for every part. Open a row to try it.
RadioGroup · all partsclassNameCSS class applied to the element, or a function that
returns a class based on the component's state.string | ((state: State) => string | undefined)styleStyle applied to the element, or a function that
returns a style object based on the component's state.React.CSSProperties | ((state: State) => React.CSSProperties | undefined)renderAllows you to replace the component's HTML element
with a different tag, or compose it with another component.React.ReactElement<unknown, string | React.JSXElementConstructor<any>> | ComponentRenderFn<HTMLProps, State>Use it in React#
What differs from the React API. Switch the framework at the top of the page.
@▢▢▢▢/react is the React 19 package. Its parts, props, data attributes and error messages are upstream Base UI's, and upstream's own tests run against it.
- Parts
Each component is its own entry point and exports one namespace named after it.
import { Switch } from '@base-ui-next/react/switch' export function Example() { return ( <Switch.Root> <Switch.Thumb /> </Switch.Root> ) }A part renders the element its API reference names, such as a
<span>forSwitch.Root. - Props and events
Props and callbacks have upstream's names and signatures:
onCheckedChange(checked, details),onOpenChange(open, details),onValueChange(value, details).detailscarriesreason,event,cancel()andallowPropagation(). Native handlers are React's (onClick,onKeyDown), andevent.preventBaseUIHandler()stops a part's own handler. - Styling
classNametakes a string or a function(state) => string;styletakes an object or a function(state) => object. The state'sdata-*attributes are on the element for CSS. renderrendertakes an element (render={<a href="/docs" />}) or a function(props, state) => elementthat spreadspropson what it returns.- Refs
refreaches the part's element. Imperative handles are ref props, as upstream:inputRef, andactionsRef({ validate }on Field and Form,{ unmount, close }on Dialog). - Binding
A part is controlled when its value prop (
checked,open,value) is set, and uncontrolled with thedefaultform (defaultChecked,defaultOpen,defaultValue). React has no two-way binding: pair the value with its change callback. - From @base-ui/reactChange the import from
@base-ui/react/<component>to@▢▢▢▢/react/<component>. - From @base-ui/reactNothing else changes: props, parts, data attributes and errors are the same.