0
0
mirror of https://github.com/twbs/bootstrap.git synced 2024-12-05 17:24:20 +01:00
Bootstrap/site/docs/4.4/components/input-group.md
2019-11-26 19:12:00 +02:00

14 KiB

layout title description group toc
docs Input group Easily extend form controls by adding text, buttons, or button groups on either side of textual inputs, custom selects, and custom file inputs. components true

Basic example

Place one add-on or button on either side of an input. You may also place one on both sides of an input. Remember to place <label>s outside the input group.

{% capture example %}

@
@example.com

$
.00
With textarea
{% endcapture %} {% include example.html content=example %}

Wrapping

Input groups wrap by default via flex-wrap: wrap in order to accommodate custom form field validation within an input group. You may disable this with .flex-nowrap.

{% capture example %}

@
{% endcapture %} {% include example.html content=example %}

Sizing

Add the relative form sizing classes to the .input-group itself and contents within will automatically resize—no need for repeating the form control size classes on each element.

Sizing on the individual input group elements isn't supported.

{% capture example %}

Small
Default
Large
{% endcapture %} {% include example.html content=example %}

Checkboxes and radios

Place any checkbox or radio option within an input group's addon instead of text.

{% capture example %}

{% endcapture %} {% include example.html content=example %}

Multiple inputs

While multiple <input>s are supported visually, validation styles are only available for input groups with a single <input>.

{% capture example %}

First and last name
{% endcapture %} {% include example.html content=example %}

Multiple addons

Multiple add-ons are supported and can be mixed with checkbox and radio input versions.

{% capture example %}

$ 0.00
$ 0.00
{% endcapture %} {% include example.html content=example %}

Button addons

{% capture example %}

Button
Button
Button Button
Button Button
{% endcapture %} {% include example.html content=example %}

Buttons with dropdowns

{% capture example %}

{% endcapture %} {% include example.html content=example %}

Segmented buttons

{% capture example %}

{% endcapture %} {% include example.html content=example %}

Custom forms

Input groups include support for custom selects and custom file inputs. Browser default versions of these are not supported.

Custom select

{% capture example %}

Choose... One Two Three
Choose... One Two Three
Button
Choose... One Two Three
Choose... One Two Three
Button
{% endcapture %} {% include example.html content=example %}

Custom file input

{% capture example %}

Upload
Upload
Button
Button
{% endcapture %} {% include example.html content=example %}

Accessibility

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 (<label> elements hidden using the .sr-only class, or use of the aria-label and aria-labelledby attributes, possibly in combination with aria-describedby) 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.