Autocomplete

A text input with suggestions that optionally complete your typing.

Import

import { Autocomplete } from '@oztix/roadie-components/autocomplete'

Examples

Default

function AutocompleteDefault() {
  const cities = [
    'Brisbane',
    'Sydney',
    'Melbourne',
    'Perth',
    'Adelaide',
    'Hobart',
    'Darwin',
    'Canberra',
    'Gold Coast',
    'Newcastle',
  ]

  return (
    <Autocomplete items={cities}>
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Type a city...' />
      </Autocomplete.InputGroup>
      <Autocomplete.Portal>
        <Autocomplete.Positioner>
          <Autocomplete.Popup>
            <Autocomplete.List>
              {(city) => (
                <Autocomplete.Item key={city} value={city}>
                  {city}
                </Autocomplete.Item>
              )}
            </Autocomplete.List>
            <Autocomplete.Empty>No cities found</Autocomplete.Empty>
          </Autocomplete.Popup>
        </Autocomplete.Positioner>
      </Autocomplete.Portal>
    </Autocomplete>
  )
}

Emphasis

<div className='grid gap-2'>
  <Autocomplete>
    <Autocomplete.InputGroup emphasis='normal'>
      <Autocomplete.Input placeholder='Normal emphasis' />
    </Autocomplete.InputGroup>
  </Autocomplete>
  <Autocomplete>
    <Autocomplete.InputGroup emphasis='subtle'>
      <Autocomplete.Input placeholder='Subtle emphasis' />
    </Autocomplete.InputGroup>
  </Autocomplete>
</div>

Sizes

<div className='grid gap-2'>
  <Autocomplete>
    <Autocomplete.InputGroup size='sm'>
      <Autocomplete.Input placeholder='Small' />
    </Autocomplete.InputGroup>
  </Autocomplete>
  <Autocomplete>
    <Autocomplete.InputGroup size='md'>
      <Autocomplete.Input placeholder='Medium (default)' />
    </Autocomplete.InputGroup>
  </Autocomplete>
  <Autocomplete>
    <Autocomplete.InputGroup size='lg'>
      <Autocomplete.Input placeholder='Large' />
    </Autocomplete.InputGroup>
  </Autocomplete>
</div>

States

<div className='grid gap-4'>
  <div className='grid gap-1'>
    <p className='text-sm text-subtle'>Default</p>
    <Autocomplete>
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Type here...' />
      </Autocomplete.InputGroup>
    </Autocomplete>
  </div>
  <div className='grid gap-1'>
    <p className='text-sm text-subtle'>Disabled</p>
    <Autocomplete disabled>
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Type here...' />
      </Autocomplete.InputGroup>
    </Autocomplete>
  </div>
</div>

Composition

With Field

Wrap Autocomplete in Field for consistent layout, labels, and error handling. Field.Label's htmlFor wires directly to the Autocomplete input — clicking the label focuses the text field.

function AutocompleteWithField() {
  const cities = [
    'Brisbane',
    'Sydney',
    'Melbourne',
    'Perth',
    'Adelaide',
    'Hobart',
    'Darwin',
    'Canberra',
  ]

  return (
    <Field>
      <Field.Label>City</Field.Label>
      <Autocomplete items={cities}>
        <Autocomplete.InputGroup>
          <Autocomplete.Input placeholder='Type a city...' />
          <Autocomplete.Clear />
        </Autocomplete.InputGroup>
        <Autocomplete.Portal>
          <Autocomplete.Positioner>
            <Autocomplete.Popup>
              <Autocomplete.List>
                {(city) => (
                  <Autocomplete.Item key={city} value={city}>
                    {city}
                  </Autocomplete.Item>
                )}
              </Autocomplete.List>
              <Autocomplete.Empty>No cities found</Autocomplete.Empty>
            </Autocomplete.Popup>
          </Autocomplete.Positioner>
        </Autocomplete.Portal>
      </Autocomplete>
    </Field>
  )
}

With trigger

function AutocompleteWithTrigger() {
  const cities = [
    'Brisbane',
    'Sydney',
    'Melbourne',
    'Perth',
    'Adelaide',
    'Hobart',
  ]

  return (
    <Autocomplete items={cities}>
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Type a city...' />
        <Autocomplete.Clear />
        <Autocomplete.Trigger />
      </Autocomplete.InputGroup>
      <Autocomplete.Portal>
        <Autocomplete.Positioner>
          <Autocomplete.Popup>
            <Autocomplete.List>
              {(city) => (
                <Autocomplete.Item key={city} value={city}>
                  {city}
                </Autocomplete.Item>
              )}
            </Autocomplete.List>
            <Autocomplete.Empty>No cities found</Autocomplete.Empty>
          </Autocomplete.Popup>
        </Autocomplete.Positioner>
      </Autocomplete.Portal>
    </Autocomplete>
  )
}

With groups

function AutocompleteWithGroups() {
  const groups = [
    {
      value: 'New South Wales',
      items: ['Sydney', 'Newcastle', 'Wollongong', 'Central Coast'],
    },
    {
      value: 'Queensland',
      items: ['Brisbane', 'Gold Coast', 'Sunshine Coast', 'Cairns'],
    },
  ]

  return (
    <Autocomplete items={groups}>
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Search by state...' />
      </Autocomplete.InputGroup>
      <Autocomplete.Portal>
        <Autocomplete.Positioner>
          <Autocomplete.Popup>
            <Autocomplete.List>
              {groups.map((group) => (
                <Autocomplete.Group key={group.value} items={group.items}>
                  <Autocomplete.GroupLabel>{group.value}</Autocomplete.GroupLabel>
                  <Autocomplete.Collection>
                    {(city) => (
                      <Autocomplete.Item key={city} value={city}>
                        {city}
                      </Autocomplete.Item>
                    )}
                  </Autocomplete.Collection>
                </Autocomplete.Group>
              ))}
            </Autocomplete.List>
            <Autocomplete.Empty>No cities found</Autocomplete.Empty>
          </Autocomplete.Popup>
        </Autocomplete.Positioner>
      </Autocomplete.Portal>
    </Autocomplete>
  )
}

With rich items

Use custom markup inside Autocomplete.Item to show metadata like venue, date, or an avatar alongside the primary label. Use itemToStringValue to control what text appears in the input when an item is selected — this includes the metadata so the user sees full context.

function AutocompleteRichItems() {
  const events = [
    { name: 'Somersault Magazine Issue 02 Launch + 1st Birthday', venue: 'QUIVR, Fortitude Valley', date: '17/04/2026, 7:00 pm' },
    { name: 'Manorism - "Something I Can\'t See" Single Launch', venue: 'Shotkickers, Thornbury', date: '17/04/2026, 7:00 pm' },
    { name: 'Little Somebodies w/ The Phosphenes + Lightkeepers Trio', venue: 'Bar Open, Fitzroy', date: '26/07/2026, 7:00 pm' },
    { name: 'Our Zebra Troy - "Something Cerebral" Album Launch', venue: 'Shotkickers, Thornbury', date: '18/04/2026, 2:00 pm' },
    { name: 'In The Pines 2026', venue: 'UWA Somerville, Crawley', date: '19/04/2026, 11:00 am' },
    { name: 'SUNSET FEST SOUTH - Tribute Band Festival', venue: 'Port Beach Brewery, North Fremantle', date: '11/04/2026, 3:00 pm' },
  ]

  return (
    <Autocomplete
      items={events}
      itemToStringValue={(event) =>
        `${event.name}${event.venue} · ${event.date}`
      }
    >
      <Autocomplete.InputGroup>
        <Autocomplete.Input placeholder='Search events...' />
        <Autocomplete.Clear />
      </Autocomplete.InputGroup>
      <Autocomplete.Portal>
        <Autocomplete.Positioner>
          <Autocomplete.Popup>
            <Autocomplete.List>
              {(event) => (
                <Autocomplete.Item key={event.name} value={event.name}>
                  <div className='grid gap-0.5 min-w-0'>
                    <span className='truncate font-medium'>{event.name}</span>
                    <span className='truncate text-xs text-subtle'>
                      {event.venue} · {event.date}
                    </span>
                  </div>
                </Autocomplete.Item>
              )}
            </Autocomplete.List>
            <Autocomplete.Empty>No events found</Autocomplete.Empty>
          </Autocomplete.Popup>
        </Autocomplete.Positioner>
      </Autocomplete.Portal>
    </Autocomplete>
  )
}

Guidelines

When to use Autocomplete

Use Autocomplete when the user is typing free text and suggestions help speed things up — but the typed value is always valid, even if it doesn't match any suggestion.

  • Address fields
  • Search bars
  • Tag input where custom values are allowed
  • Any text field where suggestions are helpful but not required

When to use Combobox or Select instead

If the user must pick from the list, use Combobox. If the list is short and fixed, use Select.

QuestionSelectComboboxAutocomplete
User types to filter?NoYesYes
Must pick from the list?YesYesNo — typed value is valid
Options from an API?NoYesYes
Custom/free-text value?NoNoYes
Primary interactionBrowse and pickSearch and pickType with suggestions
Typical list size2-15 items10-500+ itemsAny

Filtering

Pass the items prop to Autocomplete root for built-in client-side filtering. Use Autocomplete.List with a render function child to template each filtered item:

<Autocomplete items={cities}>
...
<Autocomplete.List>
{(city) => <Autocomplete.Item value={city}>{city}</Autocomplete.Item>}
</Autocomplete.List>
<Autocomplete.Empty>No results</Autocomplete.Empty>
</Autocomplete>

Autocomplete.Empty only renders when the filtered list is empty. It requires the items prop on root.

Async loading

For server-side search, update the items prop as results arrive. Use Autocomplete.Status to announce state changes to screen readers:

<Autocomplete items={results} onValueChange={(value) => fetchResults(value)}>
...
<Autocomplete.Status>{isLoading ? 'Loading...' : `${results.length} results`}</Autocomplete.Status>
</Autocomplete>

Mode

The mode prop controls how filtering and inline autocompletion behave:

  • list (default) — items are filtered as you type. The input value stays as typed.
  • both — items are filtered and the input temporarily shows the highlighted item's value (inline autocompletion).
  • inline — items are not filtered. The input temporarily shows the highlighted item's value.
  • none — items are static and the input value doesn't change based on highlighting.

Keyboard behaviour

  • Arrow keys navigate the list
  • Enter confirms the highlighted item (or submits the form if no item is highlighted)
  • Escape closes the popup
  • Typing filters the list in real time

Accessibility

  • Wrap in Field and use Field.Label to name the input — this provides automatic htmlFor wiring.
  • Autocomplete.Empty announces "no results" to screen readers automatically.
  • Autocomplete.Status is a live region — use it for async status like loading or result counts.
  • The input value is always valid — screen readers don't need to announce selection errors.

API reference

Autocomplete

Base UI
mode?"none" | "list" | "inline" | "both"

Controls how the autocomplete behaves with respect to list filtering and inline autocompletion. - `list` (default): items are dynamically filtered based on the input value. The input value does not change based on the active item. - `both`: items are dynamically filtered based on the input value, which will temporarily change based on the active item (inline autocompletion). - `inline`: items are static (not filtered), and the input value will temporarily change based on the active item (inline autocompletion). - `none`: items are static (not filtered), and the input value will not change based on the active item.

Defaults to 'list'.

autoHighlight?boolean | "always"

Whether the first matching item is highlighted automatically. - `true`: highlight after the user types and keep the highlight while the query changes. - `'always'`: always highlight the first item.

Defaults to false.

keepHighlight?boolean

Whether the highlighted item should be preserved when the pointer leaves the list.

Defaults to false.

highlightItemOnHover?boolean

Whether moving the pointer over items should highlight them. Disabling this prop allows CSS `:hover` to be differentiated from the `:focus` (`data-highlighted`) state.

Defaults to true.

defaultValue?string | number | readonly string[]

The uncontrolled input value of the autocomplete when it's initially rendered. To render a controlled autocomplete, use the `value` prop instead.

value?string | number | readonly string[]

The input value of the autocomplete. Use when controlled.

onValueChange?((value: string, eventDetails: ChangeEventDetails) => void)

Event handler called when the input value of the autocomplete changes.

submitOnItemClick?boolean

Whether clicking an item should submit the autocomplete's owning form. By default, clicking an item via a pointer or <kbd>Enter</kbd> key does not submit the owning form. Useful when the autocomplete is used as a single-field form search input.

Defaults to false.

itemToStringValue?((itemValue: unknown) => string)

When the item values are objects (`<Autocomplete.Item value={object}>`), this function converts the object value to a string representation for both display in the input and form submission. If the shape of the object is `{ value, label }`, the label will be used automatically without needing to specify this prop.

actionsRef?RefObject<AutocompleteRootActions | null>

A ref to imperative actions. - `unmount`: When specified, the autocomplete will not be unmounted when closed. Instead, the `unmount` function must be called to unmount the autocomplete manually. Useful when the autocomplete's animation is controlled by an external library.

onOpenChange?((open: boolean, eventDetails: ChangeEventDetails) => void)

Event handler called when the popup is opened or closed.

onItemHighlighted?((highlightedValue: unknown, eventDetails: HighlightEventDetails) => void)

Callback fired when an item is highlighted or unhighlighted. Receives the highlighted item value (or `undefined` if no item is highlighted) and event details with a `reason` property describing why the highlight changed. The `reason` can be: - `'keyboard'`: the highlight changed due to keyboard navigation. - `'pointer'`: the highlight changed due to pointer hovering. - `'none'`: the highlight changed programmatically.

openOnInputClick?boolean

Whether the popup opens when clicking the input.

Defaults to false.

Inherited from ComboboxRootProps

filter?((itemValue: unknown, query: string, itemToString?: ((itemValue: unknown) => string)) => boolean) | null

Filter function used to match items vs input query.

disabled?boolean

Whether the component should ignore user interaction.

Defaults to false.

name?string

Identifies the field when a form is submitted.

id?string

The id of the component.

grid?boolean

Whether list items are presented in a grid layout. When enabled, arrow keys navigate across rows and columns inferred from DOM rows.

Defaults to false.

inline?boolean

Whether the list is rendered inline without using the popup.

Defaults to false.

items?readonly any[] | readonly Group<any>[]

The items to be displayed in the list. Can be either a flat array of items or an array of groups with items.

readOnly?boolean

Whether the user should be unable to choose a different option from the popup.

Defaults to false.

required?boolean

Whether the user must choose a value before submitting a form.

Defaults to false.

defaultOpen?boolean

Whether the popup is initially open. To render a controlled popup, use the `open` prop instead.

Defaults to false.

open?boolean

Whether the popup is currently open. Use when controlled.

onOpenChangeComplete?((open: boolean) => void)

Event handler called after any animations complete when the popup is opened or closed.

loopFocus?boolean

Whether to loop keyboard focus back to the input when the end of the list is reached while using the arrow keys. The first item can then be reached by pressing <kbd>ArrowDown</kbd> again from the input, or the last item can be reached by pressing <kbd>ArrowUp</kbd> from the input. The input is always included in the focus loop per [ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/patterns/combobox/). When disabled, focus does not move when on the last element and the user presses <kbd>ArrowDown</kbd>, or when on the first element and the user presses <kbd>ArrowUp</kbd>.

Defaults to true.

inputRef?Ref<HTMLInputElement>

A ref to the hidden input element.

filteredItems?readonly any[] | readonly Group<any>[]

Filtered items to display in the list. When provided, the list will use these items instead of filtering the `items` prop internally. Use when you want to control filtering logic externally with the `useFilter()` hook.

virtualized?boolean

Whether the items are being externally virtualized.

Defaults to false.

modal?boolean

Determines if the popup enters a modal state when open. - `true`: user interaction is limited to the popup: document page scroll is locked and pointer interactions on outside elements are disabled. - `false`: user interaction with the rest of the document is allowed.

Defaults to false.

limit?number

The maximum number of items to display in the list.

Defaults to -1.

locale?LocalesArgument

The locale to use for string comparison. Defaults to the user's runtime locale.

Autocomplete.Clear

Base UI

Inherited from ComboboxClearProps

disabled?boolean

Whether the component should ignore user interaction.

Defaults to false.

keepMounted?boolean

Whether the component should remain mounted in the DOM when not visible.

Defaults to false.

Inherited from NativeButtonProps

nativeButton?boolean

Whether the component renders a native `<button>` element when replacing it via the `render` prop. Set to `false` if the rendered element is not a button (e.g. `<div>`).

Defaults to true.

Autocomplete.Collection

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.

Autocomplete.Empty

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.

Autocomplete.Group

Base UI

Inherited from ComboboxGroupProps

items?readonly any[]

Items to be rendered within this group. When provided, child `Collection` components will use these items.

Autocomplete.GroupLabel

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.

Autocomplete.Input

Base UI

Inherited from ComboboxInputProps

disabled?boolean

Whether the component should ignore user interaction.

Defaults to false.

Autocomplete.InputGroup

Base UI
size?"sm" | "md" | "lg" | null
intent?"neutral" | "brand" | "brand-secondary" | "accent" | "danger" | "success" | "warning" | "info" | null
emphasis?"normal" | "subtle" | null

Autocomplete.Item

Base UI

Inherited from ComboboxItemProps

onClick?((event: BaseUIEvent<MouseEvent<HTMLDivElement, MouseEvent>>) => void)

An optional click handler for the item when selected. It fires when clicking the item with the pointer, as well as when pressing `Enter` with the keyboard if the item is highlighted when the `Input` or `List` element has focus.

index?number

The index of the item in the list. Improves performance when specified by avoiding the need to calculate the index automatically from the DOM.

value?any

A unique value that identifies this item.

Defaults to null.

disabled?boolean

Whether the component should ignore user interaction.

Defaults to false.

Inherited from NativeButtonProps

nativeButton?boolean

Whether the component renders a native `<button>` element when replacing it via the `render` prop. Set to `false` if the rendered element is not a button (e.g. `<div>`).

Defaults to true.

Autocomplete.List

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.

Autocomplete.Popup

Base UI

Inherited from ComboboxPopupProps

initialFocus?boolean | RefObject<HTMLElement | null> | ((openType: InteractionType) => boolean | void | HTMLElement | null)

Determines the element to focus when the popup is opened. - `false`: Do not move focus. - `true`: Move focus based on the default behavior (first tabbable element or popup). - `RefObject`: Move focus to the ref element. - `function`: Called with the interaction type (`mouse`, `touch`, `pen`, or `keyboard`). Return an element to focus, `true` to use the default behavior, or `false`/`undefined` to do nothing.

finalFocus?boolean | RefObject<HTMLElement | null> | ((closeType: InteractionType) => boolean | void | HTMLElement | null)

Determines the element to focus when the popup is closed. - `false`: Do not move focus. - `true`: Move focus based on the default behavior (trigger or previously focused element). - `RefObject`: Move focus to the ref element. - `function`: Called with the interaction type (`mouse`, `touch`, `pen`, or `keyboard`). Return an element to focus, `true` to use the default behavior, or `false`/`undefined` to do nothing.

Autocomplete.Portal

Base UI

Inherited from ComboboxPortalProps

keepMounted?boolean

Whether to keep the portal mounted in the DOM while the popup is hidden.

Defaults to false.

Inherited from Props

container?HTMLElement | ShadowRoot | RefObject<HTMLElement | ShadowRoot | null> | null

A parent element to render the portal element into.

Autocomplete.Positioner

Base UI

Inherited from UseAnchorPositioningSharedParameters

anchor?any

An element to position the popup against. By default, the popup will be positioned against the trigger.

positionMethod?"absolute" | "fixed"

Determines which CSS `position` property to use.

Defaults to 'absolute'.

side?"top" | "bottom" | "left" | "right" | "inline-end" | "inline-start"

Which side of the anchor element to align the popup against. May automatically change to avoid collisions.

Defaults to 'bottom'.

sideOffset?number | OffsetFunction

Distance between the anchor and the popup in pixels. Also accepts a function that returns the distance to read the dimensions of the anchor and positioner elements, along with its side and alignment. The function takes a `data` object parameter with the following properties: - `data.anchor`: the dimensions of the anchor element with properties `width` and `height`. - `data.positioner`: the dimensions of the positioner element with properties `width` and `height`. - `data.side`: which side of the anchor element the positioner is aligned against. - `data.align`: how the positioner is aligned relative to the specified side. @example ```jsx <Positioner sideOffset={({ side, align, anchor, positioner }) => { return side === 'top' || side === 'bottom' ? anchor.height : anchor.width; }} /> ```

Defaults to 0.

align?"center" | "start" | "end"

How to align the popup relative to the specified side.

Defaults to 'center'.

alignOffset?number | OffsetFunction

Additional offset along the alignment axis in pixels. Also accepts a function that returns the offset to read the dimensions of the anchor and positioner elements, along with its side and alignment. The function takes a `data` object parameter with the following properties: - `data.anchor`: the dimensions of the anchor element with properties `width` and `height`. - `data.positioner`: the dimensions of the positioner element with properties `width` and `height`. - `data.side`: which side of the anchor element the positioner is aligned against. - `data.align`: how the positioner is aligned relative to the specified side. @example ```jsx <Positioner alignOffset={({ side, align, anchor, positioner }) => { return side === 'top' || side === 'bottom' ? anchor.width : anchor.height; }} /> ```

Defaults to 0.

collisionBoundary?any

An element or a rectangle that delimits the area that the popup is confined to.

Defaults to 'clipping-ancestors'.

collisionPadding?any

Additional space to maintain from the edge of the collision boundary.

Defaults to 5.

sticky?boolean

Whether to maintain the popup in the viewport after the anchor element was scrolled out of view.

Defaults to false.

arrowPadding?number

Minimum distance to maintain between the arrow and the edges of the popup. Use it to prevent the arrow element from hanging out of the rounded corners of a popup.

Defaults to 5.

disableAnchorTracking?boolean

Whether to disable the popup from tracking any layout shift of its positioning anchor.

Defaults to false.

collisionAvoidance?CollisionAvoidance

Determines how to handle collisions when positioning the popup. `side` controls overflow on the preferred placement axis (`top`/`bottom` or `left`/`right`): - `'flip'`: keep the requested side when it fits; otherwise try the opposite side (`top` and `bottom`, or `left` and `right`). - `'shift'`: never change side; keep the requested side and move the popup within the clipping boundary so it stays visible. - `'none'`: do not correct side-axis overflow. `align` controls overflow on the alignment axis (`start`/`center`/`end`): - `'flip'`: keep side, but swap `start` and `end` when the requested alignment overflows. - `'shift'`: keep side and requested alignment, then nudge the popup along the alignment axis to fit. - `'none'`: do not correct alignment-axis overflow. `fallbackAxisSide` controls fallback behavior on the perpendicular axis when the preferred axis cannot fit: - `'start'`: allow perpendicular fallback and try the logical start side first (`top` before `bottom`, or `left` before `right` in LTR). - `'end'`: allow perpendicular fallback and try the logical end side first (`bottom` before `top`, or `right` before `left` in LTR). - `'none'`: do not fallback to the perpendicular axis. When `side` is `'shift'`, explicitly setting `align` only supports `'shift'` or `'none'`. If `align` is omitted, it defaults to `'flip'`. @example ```jsx <Positioner collisionAvoidance={{ side: 'shift', align: 'shift', fallbackAxisSide: 'none', }} /> ```

Autocomplete.Status

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.

Autocomplete.Trigger

Base UI

Inherited from ComboboxTriggerProps

disabled?boolean

Whether the component should ignore user interaction.

Defaults to false.

Inherited from NativeButtonProps

nativeButton?boolean

Whether the component renders a native `<button>` element when replacing it via the `render` prop. Set to `false` if the rendered element is not a button (e.g. `<div>`).

Defaults to true.

Autocomplete.Value

Base UI

No additional props — forwards all standard HTML attributes to the underlying element.