0
0
mirror of https://github.com/twbs/bootstrap.git synced 2024-12-12 00:08:59 +01:00
Bootstrap/docs/4.0/components/input-group.md
2017-11-03 14:12:47 +02:00

12 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. We do not support multiple form-controls in a single input group and <label>s must come outside the input group.

{% example html %}

@

@example.com


$ .00

$ 0.00
{% endexample %}

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.

{% example html %}

@

@
{% endexample %}

Checkboxes and radio addons

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

{% example html %}

{% endexample %}

Multiple addons

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

{% example html %}

$
$ 0.00
{% endexample %}

Button addons

Buttons in input groups must wrapped in a .input-group-btn for proper alignment and sizing. This is required due to default browser styles that cannot be overridden.

{% example html %}

Go!
Go!

Hate it Love it
{% endexample %}

Buttons with dropdowns

{% example html %}

{% endexample %}

Segmented buttons

{% example html %}

{% endexample %}

Custom forms

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

Custom select

{% example html %}

Choose... One Two Three
Choose... One Two Three
Button Choose... One Two Three
Choose... One Two Three Button
{% endexample %}

Custom file input

{% example html %}

Upload
Upload
Button
Button
{% endexample %}

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.