frameworkExperience & interface

Select and Combobox

Selects and comboboxes let users choose from allowed values, but a combobox adds a popup and may support text entry, filtering, or autocomplete.

Download Markdown (.md)

01What it means

A native select presents a predefined set of choices through platform behavior. A combobox is an input with an associated popup whose options may be filtered or suggested as the user types; some comboboxes are select-only. “Dropdown” is ambiguous and does not specify these behaviors.[1][2]

02Why it matters

Choosing the simplest suitable control reduces implementation risk and makes expected keyboard, mobile, and assistive-technology behavior available by default. Complex custom comboboxes require careful state, focus, selection, and announcement handling.

03When to use it

Use a native select for a manageable predefined list where platform presentation is acceptable. Use a combobox when users benefit from typing to filter or enter suggested values. Use radios for a small set that should remain visible, and avoid either pattern for actions rather than values.

04How it works

  1. Define whether values are fixed, whether arbitrary input is allowed, and how many options users must search.
  2. Choose the simplest native control that satisfies those requirements before building a custom widget.
  3. Give the control a visible label and communicate required, invalid, expanded, and selected states.
  4. For a combobox, define filtering, autocomplete, popup navigation, selection, clearing, and Escape behavior.
  5. Test keyboards, touch, screen readers, zoom, long translations, empty matches, and asynchronous results.

05A practical example

Example

A shipping form uses a native select for a short country-region list. A separate airport field uses an editable combobox because travelers know names or codes; it filters suggestions, announces the result count, and requires selection of a valid airport.

06Where it breaks

Long native selects are slow to scan, while custom comboboxes are costly to implement reliably. Filtering can hide valid options, remote suggestions introduce latency, and ambiguous free text can appear accepted when it is not.

Common mistakes

  • Calling every popup control a dropdown and leaving behavior unspecified.
  • Replacing a reliable native select without a user need.
  • Moving DOM focus through popup options when the chosen combobox model keeps focus on the input.
  • Failing to distinguish free text from a validated selection.

07Sources

  1. Combobox PatternW3C Web Accessibility Initiative · Technical guidanceCombobox Pattern
  2. SelectGOV.UK Design System · Institutional design systemSelect
View saved topics

Start typing to search titles, definitions, categories, and frameworks.