Semantics
Addons stay presentational; inputs and buttons keep native semantics.
Composite inputs · stable · MIT
Native input, addons, and real button actions in one shell.
Install editable source
Behavior contract
Addons stay presentational; inputs and buttons keep native semantics.
Native control and button behavior.
Light and dark themes, logical RTL layout, reduced motion, responsive content, and forwarded public refs.
Source-derived reference
These public React parts are read directly from the canonical source during the documentation build.
GummyInputGroupGummyInputGroupAddonGummyInputGroupButtonGummyInputGroupControlEach exported part accepts the underlying native, Base UI, or documented Radix prop contract. Inspect the selected source below for exact generic types.
Troubleshooting
Implementation decisions
Use an input group when an adjoining control, unit, prefix, or action changes how one field is interpreted. Keep a visible field label outside decorative affixes, and ensure buttons have names that make sense without relying on position. Do not make a currency symbol, domain suffix, or reveal control part of the submitted value accidentally. Test long units, password managers, validation, zoom, and touch targets.
Live product source
The Component Lab exercises real source across default, focus, disabled, responsive, dark, reduced-motion, and RTL contexts.
Open the live Component LabInteractive inspection
Load the real component preview when you are ready to interact with its responsive, theme, and direction controls.
Editable source
The registry payload stays off the initial page request.