Loading component…
In applications
- Planned on top of it
- ResourcePicker / ProviderPicker / LocationPicker / ServicePickerplanned
Planned means not built: none of these ships today.
Loading component…
Planned means not built: none of these ships today.
What automated tests prove about each implementation — separate from whether the package itself is a finished product. Derived from the test files; how the levels are earned.
React
React setupPackage maturity: stable · Implementation verification: Beta
Angular
Angular setup · previewPackage maturity: preview · Implementation verification: Preview
This platform’s whole catalogue is verified to React beta, Angular preview. The catalogue figure is the weakest component on that platform, not an average.
npx @kinetixui/cli add comboboxnpm i @kinetixui/ui @kinetixui/tokens@kinetixui/ui on npm@kinetixui/tokens on npmThe CLI copies React source. Usage imports from @kinetixui/ui require the npm package; for copied source, use your configured local import instead.
npm i @kinetixui/angular @kinetixui/tokens@kinetixui/angular on npm@kinetixui/tokens on npmComposition · KinetixUI ships no SwiftUI component for this.
Composition · KinetixUI ships no Jetpack Compose component for this.
Composition · KinetixUI ships no Flutter component for this.
Combobox is a recipe rather than a component: a Popover holding a Command, so people can type to filter a long list and pick one value.
Reduced motion: off · your browser setting
There is no Combobox export and no combobox registry item — it is a documented composition of
Command inside a Popover. Add the two pieces it is built from:
npx @kinetixui/cli add command popoverimport { Command, Popover, Button } from "@kinetixui/ui";Styled entirely from the KinetixUI token contract — bg-action,
text-muted-foreground, border-input, ring-ring. Works in light and dark
with no extra config. Keyboard and ARIA behaviour is inherited from Radix where the
component is built on a primitive; the hand-built widgets (DataGrid, TreeView,
ColorPicker, MultiSelect, Tour, KanbanBoard) have their own documented interaction
models — see Accessibility.