Aliases
autocomplete, filterable select
components / combobox
Filterable field-and-list control for faster option discovery when scanning a full menu is too heavy.
Playground
Start here. Switch systems, interact with the shipped component, and let the rest of the page answer the why and how after the behavior clicks.
Cobalt
The crisp default DK action system: bright primary, roomy spacing, and a direct editorial rhythm.
Overview
This section explains the intent of the component before the implementation details.
Aliases
autocomplete, filterable select
Explore the math
Decision guide
Use these notes to decide quickly whether this is the right DK component for the job.
Decision guide
Do
Do not
Usage
Prefer these situations when choosing this component.
Usage
These patterns are better served by a different component or a simpler surface.
Anti-patterns
Migration notes
Anatomy
The anatomy explains which pieces matter to the recipe and accessibility model.
field wrapper
rootProvides label, description, and shell treatment.
combobox input
inputReceives the typed filter text and current selection label.
anchored options surface
listboxShows the filtered option set.
list option
optionSelectable option row with label and optional description.
API
The docs contract distinguishes props, DOM events, and slots so integration behavior is explicit.
Props
| Name | Type | Default | Description |
|---|---|---|---|
label | string | — | Visible label used for the field or control. |
description | string | — | Supporting helper copy rendered below or beside the main label. |
error | string | — | Validation or problem copy rendered in the error slot when present. |
placeholder | string | — | Placeholder text shown before a user makes a selection or enters text. |
required | boolean | false | Marks the field or control as required for form semantics and docs examples. |
disabled | boolean | false | Disables interaction and exposes the correct non-interactive semantics for the control. |
name | string | — | Form field name used for native form submission. |
id | string | — | Optional id used to bind external labels or descriptions to the component. |
size | 'sm' | 'md' | 'lg' | 'md' | Chooses the compiled size recipe for the component. |
items | Array<{ value: string; label: string; description?: string; disabled?: boolean }> | — | Available options rendered inside the listbox. |
value | string | — | Controlled selected value. |
onChange | (detail: { value: string | undefined }) => void | — | Callback fired when a selection is committed. |
theme | ThemeContract | — | Overrides the compiled DK theme used to resolve tokens and recipes for this component. |
Events
| Name | Payload | Description |
|---|---|---|
change | { value: string | undefined } | Fires when the component commits a new value. |
Slots
| Name | Description |
|---|---|
default | Combobox is data-driven in v1 and does not expose option slots. |
Recipes
These notes summarize the intended recipe surface rather than exposing raw implementation detail first.
Variants
Sizes
States
Accessibility
This is the behavior the component promises to assistive tech and keyboard users today.
Semantics
Keyboard
Screen readers
Checklist
Implementation
This section shows the representative compiled slot variables that the runtime consumes for the selected design system.
Implementation notes
Implementation checklist
Examples
Each example is intentionally practical, grouped by starter, common pattern, and edge-case coverage.
Starter
1 example
starter
Starter: searchable preset pickerA searchable field for moderate preset lists.
Copy snippet
<Combobox label="Choose a system" description="Filter by name or personality." items={systems} />Common patterns
1 example
common
Common: compact tool pickerSmaller size works well in dense operational tools.
Copy snippet
<Combobox size="sm" label="Preset" placeholder="Find preset" items={systems} />Edge cases
1 example
edge
Edge: controlled selectionControl the selected value when the surrounding app owns the state.
Copy snippet
<Combobox label="Preset" items={systems} value={selectedPreset} onChange={(detail) => selectedPreset = detail.value} />Verification
Proofs stay visible in the docs so the system shows what it can guarantee, not just what it can render.
size=sm
size=md
size=lg
size=sm
size=md
size=lg
size=sm
size=md
size=lg