Extend form controls by adding text or buttons before, after, or on both sides of any text-based
.input-group with an
.input-group-btn to prepend or append elements to a single
<select> elements here as they cannot be fully styled in WebKit browsers.
<textarea> elements here as their
rows attribute will not be respected in some cases.
When using tooltips or popovers on elements within an
.input-group, you'll have to specify the option
container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).
Do not mix form groups or grid column classes directly with input groups. Instead, nest the input group inside of the form group or grid-related element.
Screen readers will have trouble with your forms if you don't include a label for every input. For these input groups, ensure that any additional label or functionality is conveyed to assistive technologies.
The exact technique to be used (visible
<label> elements hidden using the
.sr-only class, or use of the
placeholder attribute) and what additional information will need to be conveyed will vary depending on the exact type of interface widget you're implementing. The examples in this section provide a few suggested, case-specific approaches.
Place one add-on or button on either side of an input. You may also place one on both sides of an input.
We do not support multiple add-ons (
.input-group-btn) on a single side.
We do not support multiple form-controls in a single input group.