2014-07-12 07:34:47 +02:00
---
2015-08-15 07:45:55 +02:00
layout: docs
2014-07-12 07:34:47 +02:00
title: Forms
2017-05-28 08:01:14 +02:00
description: Examples and usage guidelines for form control styles, layout options, and custom components for creating a wide variety of forms.
2015-08-06 02:47:45 +02:00
group: components
2017-05-28 08:01:14 +02:00
toc: true
2014-07-12 07:34:47 +02:00
---
2017-06-14 07:11:44 +02:00
## Overview
2014-07-12 07:34:47 +02:00
2017-06-14 07:13:05 +02:00
Bootstrap's form controls expand on [our Rebooted form styles ]({{ site.baseurl }}/docs/{{ site.docs_version }}/content/reboot/#forms ) with classes. Use these classes to opt into their customized displays for a more consistent rendering across browsers and devices.
2014-07-12 07:34:47 +02:00
2017-06-14 07:11:44 +02:00
Be sure to use an appropriate `type` attribute on all inputs (e.g., `email` for email address or `number` for numerical information) to take advantage of newer input controls like email verification, number selection, and more.
Here's a quick example to demonstrate Bootstrap's form styles. Keep reading for documentation on required classes, form layout, and more.
2017-05-27 06:54:25 +02:00
2014-07-12 07:34:47 +02:00
{% example html %}
2014-12-01 05:17:45 +01:00
< form >
2016-02-19 15:57:26 +01:00
< div class = "form-group" >
2014-03-17 03:03:53 +01:00
< label for = "exampleInputEmail1" > Email address< / label >
2015-12-24 11:11:33 +01:00
< input type = "email" class = "form-control" id = "exampleInputEmail1" aria-describedby = "emailHelp" placeholder = "Enter email" >
2016-05-10 17:24:38 +02:00
< small id = "emailHelp" class = "form-text text-muted" > We'll never share your email with anyone else.< / small >
2016-02-19 15:57:26 +01:00
< / div >
< div class = "form-group" >
2014-03-17 03:03:53 +01:00
< label for = "exampleInputPassword1" > Password< / label >
< input type = "password" class = "form-control" id = "exampleInputPassword1" placeholder = "Password" >
2016-02-19 15:57:26 +01:00
< / div >
2017-06-14 07:11:44 +02:00
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input type = "checkbox" class = "form-check-input" id = "exampleCheck1" >
< label class = "form-check-label" for = "exampleCheck1" > Check me out< / label >
2017-06-14 07:11:44 +02:00
< / div >
< button type = "submit" class = "btn btn-primary" > Submit< / button >
< / form >
{% endexample %}
## Form controls
Textual form controls—like `<input>` s, `<select>` s, and `<textarea>` s—are styled with the `.form-control` class. Included are styles for general appearance, focus state, sizing, and more.
Be sure to explore our [custom forms ](#custom-forms ) to further style `<select>` s.
{% example html %}
< form >
< div class = "form-group" >
< label for = "exampleFormControlInput1" > Email address< / label >
< input type = "email" class = "form-control" id = "exampleFormControlInput1" placeholder = "name@example.com" >
< / div >
2016-02-19 15:57:26 +01:00
< div class = "form-group" >
2017-06-14 07:11:44 +02:00
< label for = "exampleFormControlSelect1" > Example select< / label >
< select class = "form-control" id = "exampleFormControlSelect1" >
2015-04-18 01:02:41 +02:00
< option > 1< / option >
< option > 2< / option >
< option > 3< / option >
< option > 4< / option >
< option > 5< / option >
< / select >
2016-02-19 15:57:26 +01:00
< / div >
< div class = "form-group" >
2017-06-14 07:11:44 +02:00
< label for = "exampleFormControlSelect2" > Example multiple select< / label >
< select multiple class = "form-control" id = "exampleFormControlSelect2" >
2015-04-18 01:02:41 +02:00
< option > 1< / option >
< option > 2< / option >
< option > 3< / option >
< option > 4< / option >
< option > 5< / option >
< / select >
2016-02-19 15:57:26 +01:00
< / div >
< div class = "form-group" >
2017-06-14 07:11:44 +02:00
< label for = "exampleFormControlTextarea1" > Example textarea< / label >
< textarea class = "form-control" id = "exampleFormControlTextarea1" rows = "3" > < / textarea >
2016-02-19 15:57:26 +01:00
< / div >
2017-06-14 07:11:44 +02:00
< / form >
{% endexample %}
For file inputs, swap the `.form-control` for `.form-control-file` .
{% example html %}
< form >
2016-02-19 15:57:26 +01:00
< div class = "form-group" >
2017-06-14 07:11:44 +02:00
< label for = "exampleFormControlFile1" > Example file input< / label >
< input type = "file" class = "form-control-file" id = "exampleFormControlFile1" >
2014-03-17 03:03:53 +01:00
< / div >
2017-06-14 07:11:44 +02:00
< / form >
{% endexample %}
### Sizing
Set heights using classes like `.form-control-lg` and `.form-control-sm` .
{% example html %}
< input class = "form-control form-control-lg" type = "text" placeholder = ".form-control-lg" >
< input class = "form-control" type = "text" placeholder = "Default input" >
< input class = "form-control form-control-sm" type = "text" placeholder = ".form-control-sm" >
{% endexample %}
{% example html %}
< select class = "form-control form-control-lg" >
< option > Large select< / option >
< / select >
< select class = "form-control" >
< option > Default select< / option >
< / select >
< select class = "form-control form-control-sm" >
< option > Small select< / option >
< / select >
{% endexample %}
### Readonly
Add the `readonly` boolean attribute on an input to prevent modification of the input's value. Read-only inputs appear lighter (just like disabled inputs), but retain the standard cursor.
{% example html %}
< input class = "form-control" type = "text" placeholder = "Readonly input here…" readonly >
{% endexample %}
2017-04-28 01:35:55 +02:00
### Readonly plain text
2017-06-14 07:11:44 +02:00
2017-04-28 01:35:55 +02:00
If you want to have `<input readonly>` elements in your form styled as plain text, use the `.form-control-plaintext` class to remove the default form field styling and preserve the correct margin and padding.
2017-06-14 07:11:44 +02:00
{% example html %}
< form >
< div class = "form-group row" >
< label for = "staticEmail" class = "col-sm-2 col-form-label" > Email< / label >
< div class = "col-sm-10" >
2017-04-28 01:35:55 +02:00
< input type = "text" readonly class = "form-control-plaintext" id = "staticEmail" value = "email@example.com" >
2016-02-19 15:57:26 +01:00
< / div >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-group row" >
< label for = "inputPassword" class = "col-sm-2 col-form-label" > Password< / label >
< div class = "col-sm-10" >
< input type = "password" class = "form-control" id = "inputPassword" placeholder = "Password" >
2016-02-19 15:57:26 +01:00
< / div >
2014-03-17 03:03:53 +01:00
< / div >
< / form >
2014-07-12 07:34:47 +02:00
{% endexample %}
2014-03-17 03:03:53 +01:00
2017-06-14 07:11:44 +02:00
{% example html %}
< form class = "form-inline" >
2017-10-27 14:55:07 +02:00
< div class = "form-group mb-2" >
2017-06-14 07:11:44 +02:00
< label for = "staticEmail2" class = "sr-only" > Email< / label >
2017-04-28 01:35:55 +02:00
< input type = "text" readonly class = "form-control-plaintext" id = "staticEmail2" value = "email@example.com" >
2017-06-14 07:11:44 +02:00
< / div >
2017-10-27 14:55:07 +02:00
< div class = "form-group mx-sm-3 mb-2" >
2017-06-14 07:11:44 +02:00
< label for = "inputPassword2" class = "sr-only" > Password< / label >
< input type = "password" class = "form-control" id = "inputPassword2" placeholder = "Password" >
< / div >
2017-10-27 14:55:07 +02:00
< button type = "submit" class = "btn btn-primary mb-2" > Confirm identity< / button >
2017-06-14 07:11:44 +02:00
< / form >
{% endexample %}
## Checkboxes and radios
Default checkboxes and radios are improved upon with the help of `.form-check` , **a single class for both input types that improves the layout and behavior of their HTML elements** . Checkboxes are for selecting one or several options in a list, while radios are for selecting one option from many.
2017-12-23 01:13:01 +01:00
Disabled checkboxes and radios are supported, but to provide a `not-allowed` cursor on hover of the parent `<label>` , you'll need to add the `disabled` attribute to the `.form-check-input` . The disabled attribute will apply a lighter color to help indicate the input's state.
Checkboxes and radios use are built to support HTML-based form validation and provide concise, accessible labels. As such, our `<input>` s and `<label>` s are sibling elements as opposed to an `<input>` within a `<label>` . This is slightly more verbose as you must specify `id` and `for` attributes to relate the `<input>` and `<label>` .
2017-06-14 07:11:44 +02:00
### Default (stacked)
By default, any number of checkboxes and radios that are immediate sibling will be vertically stacked and appropriately spaced with `.form-check` .
{% example html %}
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" value = "" id = "defaultCheck1" >
< label class = "form-check-label" for = "defaultCheck1" >
Default checkbox
2017-06-14 07:11:44 +02:00
< / label >
< / div >
2017-12-23 01:13:01 +01:00
< div class = "form-check" >
< input class = "form-check-input" type = "checkbox" value = "" id = "defaultCheck2" disabled >
< label class = "form-check-label" for = "defaultCheck2" >
Disabled checkbox
2017-06-14 07:11:44 +02:00
< / label >
< / div >
{% endexample %}
{% example html %}
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "exampleRadios" id = "exampleRadios1" value = "option1" checked >
< label class = "form-check-label" for = "exampleRadios1" >
Default radio
2017-06-14 07:11:44 +02:00
< / label >
< / div >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "exampleRadios" id = "exampleRadios2" value = "option2" >
< label class = "form-check-label" for = "exampleRadios2" >
Second default radio
2017-06-14 07:11:44 +02:00
< / label >
< / div >
< div class = "form-check disabled" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "exampleRadios" id = "exampleRadios3" value = "option3" disabled >
< label class = "form-check-label" for = "exampleRadios3" >
Disabled radio
2017-06-14 07:11:44 +02:00
< / label >
< / div >
{% endexample %}
### Inline
Group checkboxes or radios on the same horizontal row by adding `.form-check-inline` to any `.form-check` .
{% example html %}
< div class = "form-check form-check-inline" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "inlineCheckbox1" value = "option1" >
< label class = "form-check-label" for = "inlineCheckbox1" > 1< / label >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-check form-check-inline" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "inlineCheckbox2" value = "option2" >
< label class = "form-check-label" for = "inlineCheckbox2" > 2< / label >
2017-06-14 07:11:44 +02:00
< / div >
2017-12-23 01:13:01 +01:00
< div class = "form-check form-check-inline" >
< input class = "form-check-input" type = "checkbox" id = "inlineCheckbox3" value = "option3" disabled >
< label class = "form-check-label" for = "inlineCheckbox3" > 3 (disabled)< / label >
2017-06-14 07:11:44 +02:00
< / div >
{% endexample %}
{% example html %}
< div class = "form-check form-check-inline" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "inlineRadioOptions" id = "inlineRadio1" value = "option1" >
< label class = "form-check-label" for = "inlineRadio1" > 1< / label >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-check form-check-inline" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "inlineRadioOptions" id = "inlineRadio2" value = "option2" >
< label class = "form-check-label" for = "inlineRadio2" > 2< / label >
2017-06-14 07:11:44 +02:00
< / div >
2017-12-23 01:13:01 +01:00
< div class = "form-check form-check-inline" >
< input class = "form-check-input" type = "radio" name = "inlineRadioOptions" id = "inlineRadio3" value = "option3" disabled >
< label class = "form-check-label" for = "inlineRadio3" > 3 (disabled)< / label >
2017-06-14 07:11:44 +02:00
< / div >
{% endexample %}
### Without labels
2017-08-08 07:25:35 +02:00
Add `.position-static` to inputs within `.form-check` that don't have any label text. Remember to still provide some form of label for assistive technologies (for instance, using `aria-label` ).
2017-06-14 07:11:44 +02:00
{% example html %}
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input position-static" type = "checkbox" id = "blankCheckbox" value = "option1" aria-label = "..." >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input position-static" type = "radio" name = "blankRadio" id = "blankRadio1" value = "option1" aria-label = "..." >
2017-06-14 07:11:44 +02:00
< / div >
{% endexample %}
2016-01-07 00:52:12 +01:00
2017-05-27 23:38:37 +02:00
## Layout
2015-04-18 01:02:41 +02:00
Since Bootstrap applies `display: block` and `width: 100%` to almost all our form controls, forms will by default stack vertically. Additional classes can be used to vary this layout on a per-form basis.
### Form groups
2015-09-07 16:07:35 +02:00
The `.form-group` class is the easiest way to add some structure to forms. Its only purpose is to provide `margin-bottom` around a label and control pairing. As a bonus, since it's a class you can use it with `<fieldset>` s, `<div>` s, or nearly any other element.
2014-07-12 07:34:47 +02:00
2015-04-18 01:02:41 +02:00
{% example html %}
< form >
2016-02-19 15:57:26 +01:00
< div class = "form-group" >
2017-11-15 02:37:23 +01:00
< label for = "formGroupExampleInput" > Example label< / label >
2015-04-18 01:02:41 +02:00
< input type = "text" class = "form-control" id = "formGroupExampleInput" placeholder = "Example input" >
2016-02-19 15:57:26 +01:00
< / div >
< div class = "form-group" >
2017-11-15 02:37:23 +01:00
< label for = "formGroupExampleInput2" > Another label< / label >
2015-04-18 01:02:41 +02:00
< input type = "text" class = "form-control" id = "formGroupExampleInput2" placeholder = "Another input" >
2016-02-19 15:57:26 +01:00
< / div >
2015-04-18 01:02:41 +02:00
< / form >
{% endexample %}
2017-06-14 07:11:44 +02:00
### Form grid
More complex forms can be built using our grid classes. Use these for form layouts that require multiple columns, varied widths, and additional alignment options.
2017-05-27 05:15:30 +02:00
{% example html %}
< form >
2017-06-14 07:11:44 +02:00
< div class = "row" >
2017-05-27 05:15:30 +02:00
< div class = "col" >
< input type = "text" class = "form-control" placeholder = "First name" >
< / div >
< div class = "col" >
< input type = "text" class = "form-control" placeholder = "Last name" >
< / div >
< / div >
< / form >
2017-06-14 07:11:44 +02:00
{% endexample %}
#### Form row
You may also swap `.row` for `.form-row` , a variation of our standard grid row that overrides the default column gutters for tighter and more compact layouts.
2017-05-27 05:15:30 +02:00
{% example html %}
< form >
2017-06-14 07:11:44 +02:00
< div class = "form-row" >
2017-05-27 05:15:30 +02:00
< div class = "col" >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" placeholder = "First name" >
2017-05-27 05:15:30 +02:00
< / div >
< div class = "col" >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" placeholder = "Last name" >
2017-05-27 05:15:30 +02:00
< / div >
< / div >
< / form >
2017-06-14 07:11:44 +02:00
{% endexample %}
More complex layouts can also be created with the grid system.
2017-05-27 05:15:30 +02:00
{% example html %}
< form >
2017-06-14 07:11:44 +02:00
< div class = "form-row" >
< div class = "form-group col-md-6" >
2017-10-18 18:59:30 +02:00
< label for = "inputEmail4" > Email< / label >
2017-06-14 07:11:44 +02:00
< input type = "email" class = "form-control" id = "inputEmail4" placeholder = "Email" >
2017-05-27 05:15:30 +02:00
< / div >
2017-06-14 07:11:44 +02:00
< div class = "form-group col-md-6" >
2017-10-18 18:59:30 +02:00
< label for = "inputPassword4" > Password< / label >
2017-06-14 07:11:44 +02:00
< input type = "password" class = "form-control" id = "inputPassword4" placeholder = "Password" >
2017-05-27 05:15:30 +02:00
< / div >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-group" >
2017-10-18 18:59:30 +02:00
< label for = "inputAddress" > Address< / label >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" id = "inputAddress" placeholder = "1234 Main St" >
< / div >
< div class = "form-group" >
2017-10-18 18:59:30 +02:00
< label for = "inputAddress2" > Address 2< / label >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" id = "inputAddress2" placeholder = "Apartment, studio, or floor" >
< / div >
< div class = "form-row" >
< div class = "form-group col-md-6" >
2017-10-18 18:59:30 +02:00
< label for = "inputCity" > City< / label >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" id = "inputCity" >
2017-05-27 05:15:30 +02:00
< / div >
2017-06-14 07:11:44 +02:00
< div class = "form-group col-md-4" >
2017-10-18 18:59:30 +02:00
< label for = "inputState" > State< / label >
2017-09-12 23:29:09 +02:00
< select id = "inputState" class = "form-control" >
< option selected > Choose...< / option >
< option > ...< / option >
< / select >
2017-06-14 07:11:44 +02:00
< / div >
< div class = "form-group col-md-2" >
2017-10-18 18:59:30 +02:00
< label for = "inputZip" > Zip< / label >
2017-06-14 07:11:44 +02:00
< input type = "text" class = "form-control" id = "inputZip" >
< / div >
< / div >
< div class = "form-group" >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "gridCheck" >
< label class = "form-check-label" for = "gridCheck" >
Check me out
2017-06-14 07:11:44 +02:00
< / label >
2017-05-27 05:15:30 +02:00
< / div >
< / div >
2017-06-14 07:11:44 +02:00
< button type = "submit" class = "btn btn-primary" > Sign in< / button >
2017-05-27 05:15:30 +02:00
< / form >
{% endexample %}
2017-06-14 07:11:44 +02:00
#### Horizontal form
Remove .col-form-legend in favor of .col-form-label (#24932)
* chore: sync with twbs (#1)
* Make styling of grouped option buttons class-based
Referencing #23728, styling grouped radio and checkbox buttons should not require the data-toggle attribute.
* Fix installing deps in our webpack docs
* Fix nested cards on card group (#24766)
* Update popper.js to v1.12.9. (#24797)
* Don't run postcss for `dist/css/*.min.css` files. (#24676)
* Change the text color to dark on bg color warning examples (#24805)
* Remove unused file and bundle ie-emulation-modes-warning.js with docs.min.js (#24825)
* Remove the unused assets/js/ie10-viewport-bug-workaround.js.
* Combine ie-emulation-modes-warning.js with docs.min.js.
* Typos in grid.md (#24828)
Fixed typos in offsetting section of grid.md
* Fix dropup example code
* Update devDependencies. (#24829)
* Add support for fractional viewport widths (zoom/high-dpi displays) (#24299)
* Change breakpoint max- calculation to fractional values
* Update docs to reflect fractional max-width breakpoint values
* Add fractional max-width to offcanvas example
* Add documentation and SCSS comment for fractional viewport support
* Add a simple script to generate SRI hashes for our assets. (#24814)
* Allow us to run our unit test on differents jquery version
* Run karma tests in parallel.
* Update typography docs (#24863)
* closes #24450
* Rewrite custom form check backgrounds (#24697)
* Rewrite custom form check backgrounds
Previously, this was all just a background-color and background-image. When we restored the gradients though, we had two background-images competing on the same element, causing rendering glitches. This refactors that code, creating a mixin to simplify things, so we can we easily use two background-images (SVG icon and gradient) when -gradients is set to true.
Fixes #24598
* restore default vars
* Revamp custom check and radio backgrounds
Instead of applying multiple background-image's to the same element, we're adding a new ::before pseudo-element to layer the background-images. Gradients go on the .custom-control-indicator while their icons go on the ::before element. This allows us to shave some bytes from when we compile and we previously needed to redeclare the background-image for the icon if you changed the gradient.
* remove now unused mixin
* mention change in migration docs
* lets the centered modal have any height (#24803)
* Custom select updates (#24699)
* Add support for size attribute on custom selects
* Add large custom select, document it and the small variant
* fix custom select focus state
* fix custom file input focus styles
* remove empty line
* Update package.json. (#24582)
1. Use the same jQuery version in jspm
2. Update the files to only include the source and dist folders
* Use Jekyll's `smartify` filter when possible. (#24866)
* Darken outline hover color to match default button hover (#24150)
* Fix Issue #24144
Alter button-outline-variant mixin to darken hover and active background in same fashion as filled button.
* Fix Issue #24144
Filled button on hover should utilize the same color-yiq mixin so that theme buttons match
* default values, fix mixin
* rename it
* document it
* add migration note
* fixes #24728
* Remove unused CSS. (#24872)
* tab.js: do not remove fade class if there's no initial active pane
* Restore currently unused variables (#24891)
* Replace lint-vars.sh with a Node.js script. (#24860)
Also, include it in the `css` npm script since it's instant.
* Fix docs horizontal scrollbar (#24878)
* Fix docs horizontal scrollbar in Components > Modal
* Add overflow to docs example class
* Drop the handleUpdate() variant
While I understand the variant covers the "get a particular plugin instance" case from http://getbootstrap.com/docs/4.0/getting-started/javascript/#programmatic-api it seems weird that we do it here but not everywhere else in the docs (randomly checking other pages, we seem to stick to the documented methods as written on those pages). As this isn't properly explained as is, and as it adds nothing (more of a preference for authors), it would be easier to just drop the variant and stick with the documented method as outlined later on in the same page (avoids having to go off on a "why should you use this instead of that" tangent here).
* Combine path and remove variable used in one place. (#24873)
* Update devDependencies and gems. (#24876)
* Override padding on radio input label (#24899)
We could tell folks to nix the class, we could tell them to override it, or we could add another modifier of some kind to address this. None of them seem particularly useful, but the padding override feels the most approachable and clearly documentable. Added this here to close #24844.
* Update README.md (#24912)
* Work around Travis failures.
Note that we should revert this when the issue is fixed.
* Revert the Travis workaround. (#24926)
The issue has been fixed.
* add .col-form-legend-lg and .col-form-legend-sm classes
* document .col-form-legend-{size}
* trash .col-form-legend completely
One class fits all
* Update forms.md
* consolidate copy
* property order
2017-12-02 20:51:38 +01:00
Create horizontal forms with the grid by adding the `.row` class to form groups and using the `.col-*-*` classes to specify the width of your labels and controls. Be sure to add `.col-form-label` to your `<label>` s as well so they're vertically centered with their associated form controls.
2017-06-14 07:11:44 +02:00
2017-11-29 12:05:01 +01:00
At times, you maybe need to use margin or padding utilities to create that perfect alignment you need. For example, we've removed the `padding-top` on our stacked radio inputs label to better align the text baseline.
2017-05-27 05:15:30 +02:00
{% example html %}
2017-10-18 19:11:35 +02:00
< form >
< div class = "form-group row" >
< label for = "inputEmail3" class = "col-sm-2 col-form-label" > Email< / label >
< div class = "col-sm-10" >
< input type = "email" class = "form-control" id = "inputEmail3" placeholder = "Email" >
2017-06-14 07:11:44 +02:00
< / div >
2017-10-18 19:11:35 +02:00
< / div >
< div class = "form-group row" >
< label for = "inputPassword3" class = "col-sm-2 col-form-label" > Password< / label >
< div class = "col-sm-10" >
< input type = "password" class = "form-control" id = "inputPassword3" placeholder = "Password" >
2017-06-14 07:11:44 +02:00
< / div >
2017-10-18 19:11:35 +02:00
< / div >
< fieldset class = "form-group" >
< div class = "row" >
Remove .col-form-legend in favor of .col-form-label (#24932)
* chore: sync with twbs (#1)
* Make styling of grouped option buttons class-based
Referencing #23728, styling grouped radio and checkbox buttons should not require the data-toggle attribute.
* Fix installing deps in our webpack docs
* Fix nested cards on card group (#24766)
* Update popper.js to v1.12.9. (#24797)
* Don't run postcss for `dist/css/*.min.css` files. (#24676)
* Change the text color to dark on bg color warning examples (#24805)
* Remove unused file and bundle ie-emulation-modes-warning.js with docs.min.js (#24825)
* Remove the unused assets/js/ie10-viewport-bug-workaround.js.
* Combine ie-emulation-modes-warning.js with docs.min.js.
* Typos in grid.md (#24828)
Fixed typos in offsetting section of grid.md
* Fix dropup example code
* Update devDependencies. (#24829)
* Add support for fractional viewport widths (zoom/high-dpi displays) (#24299)
* Change breakpoint max- calculation to fractional values
* Update docs to reflect fractional max-width breakpoint values
* Add fractional max-width to offcanvas example
* Add documentation and SCSS comment for fractional viewport support
* Add a simple script to generate SRI hashes for our assets. (#24814)
* Allow us to run our unit test on differents jquery version
* Run karma tests in parallel.
* Update typography docs (#24863)
* closes #24450
* Rewrite custom form check backgrounds (#24697)
* Rewrite custom form check backgrounds
Previously, this was all just a background-color and background-image. When we restored the gradients though, we had two background-images competing on the same element, causing rendering glitches. This refactors that code, creating a mixin to simplify things, so we can we easily use two background-images (SVG icon and gradient) when -gradients is set to true.
Fixes #24598
* restore default vars
* Revamp custom check and radio backgrounds
Instead of applying multiple background-image's to the same element, we're adding a new ::before pseudo-element to layer the background-images. Gradients go on the .custom-control-indicator while their icons go on the ::before element. This allows us to shave some bytes from when we compile and we previously needed to redeclare the background-image for the icon if you changed the gradient.
* remove now unused mixin
* mention change in migration docs
* lets the centered modal have any height (#24803)
* Custom select updates (#24699)
* Add support for size attribute on custom selects
* Add large custom select, document it and the small variant
* fix custom select focus state
* fix custom file input focus styles
* remove empty line
* Update package.json. (#24582)
1. Use the same jQuery version in jspm
2. Update the files to only include the source and dist folders
* Use Jekyll's `smartify` filter when possible. (#24866)
* Darken outline hover color to match default button hover (#24150)
* Fix Issue #24144
Alter button-outline-variant mixin to darken hover and active background in same fashion as filled button.
* Fix Issue #24144
Filled button on hover should utilize the same color-yiq mixin so that theme buttons match
* default values, fix mixin
* rename it
* document it
* add migration note
* fixes #24728
* Remove unused CSS. (#24872)
* tab.js: do not remove fade class if there's no initial active pane
* Restore currently unused variables (#24891)
* Replace lint-vars.sh with a Node.js script. (#24860)
Also, include it in the `css` npm script since it's instant.
* Fix docs horizontal scrollbar (#24878)
* Fix docs horizontal scrollbar in Components > Modal
* Add overflow to docs example class
* Drop the handleUpdate() variant
While I understand the variant covers the "get a particular plugin instance" case from http://getbootstrap.com/docs/4.0/getting-started/javascript/#programmatic-api it seems weird that we do it here but not everywhere else in the docs (randomly checking other pages, we seem to stick to the documented methods as written on those pages). As this isn't properly explained as is, and as it adds nothing (more of a preference for authors), it would be easier to just drop the variant and stick with the documented method as outlined later on in the same page (avoids having to go off on a "why should you use this instead of that" tangent here).
* Combine path and remove variable used in one place. (#24873)
* Update devDependencies and gems. (#24876)
* Override padding on radio input label (#24899)
We could tell folks to nix the class, we could tell them to override it, or we could add another modifier of some kind to address this. None of them seem particularly useful, but the padding override feels the most approachable and clearly documentable. Added this here to close #24844.
* Update README.md (#24912)
* Work around Travis failures.
Note that we should revert this when the issue is fixed.
* Revert the Travis workaround. (#24926)
The issue has been fixed.
* add .col-form-legend-lg and .col-form-legend-sm classes
* document .col-form-legend-{size}
* trash .col-form-legend completely
One class fits all
* Update forms.md
* consolidate copy
* property order
2017-12-02 20:51:38 +01:00
< legend class = "col-form-label col-sm-2 pt-0" > Radios< / legend >
2017-06-14 07:11:44 +02:00
< div class = "col-sm-10" >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "gridRadios" id = "gridRadios1" value = "option1" checked >
< label class = "form-check-label" for = "gridRadios1" >
First radio
2017-10-18 19:11:35 +02:00
< / label >
< / div >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "gridRadios" id = "gridRadios2" value = "option2" >
< label class = "form-check-label" for = "gridRadios2" >
Second radio
2017-10-18 19:11:35 +02:00
< / label >
< / div >
< div class = "form-check disabled" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "radio" name = "gridRadios" id = "gridRadios3" value = "option3" disabled >
< label class = "form-check-label" for = "gridRadios3" >
Third disabled radio
2017-06-14 07:11:44 +02:00
< / label >
< / div >
< / div >
< / div >
2017-10-18 19:11:35 +02:00
< / fieldset >
< div class = "form-group row" >
< div class = "col-sm-2" > Checkbox< / div >
< div class = "col-sm-10" >
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "gridCheck1" >
< label class = "form-check-label" for = "gridCheck1" >
Example checkbox
2017-10-18 19:11:35 +02:00
< / label >
2017-06-14 07:11:44 +02:00
< / div >
< / div >
2017-10-18 19:11:35 +02:00
< / div >
< div class = "form-group row" >
< div class = "col-sm-10" >
< button type = "submit" class = "btn btn-primary" > Sign in< / button >
< / div >
< / div >
< / form >
{% endexample %}
##### Horizontal form label sizing
Remove .col-form-legend in favor of .col-form-label (#24932)
* chore: sync with twbs (#1)
* Make styling of grouped option buttons class-based
Referencing #23728, styling grouped radio and checkbox buttons should not require the data-toggle attribute.
* Fix installing deps in our webpack docs
* Fix nested cards on card group (#24766)
* Update popper.js to v1.12.9. (#24797)
* Don't run postcss for `dist/css/*.min.css` files. (#24676)
* Change the text color to dark on bg color warning examples (#24805)
* Remove unused file and bundle ie-emulation-modes-warning.js with docs.min.js (#24825)
* Remove the unused assets/js/ie10-viewport-bug-workaround.js.
* Combine ie-emulation-modes-warning.js with docs.min.js.
* Typos in grid.md (#24828)
Fixed typos in offsetting section of grid.md
* Fix dropup example code
* Update devDependencies. (#24829)
* Add support for fractional viewport widths (zoom/high-dpi displays) (#24299)
* Change breakpoint max- calculation to fractional values
* Update docs to reflect fractional max-width breakpoint values
* Add fractional max-width to offcanvas example
* Add documentation and SCSS comment for fractional viewport support
* Add a simple script to generate SRI hashes for our assets. (#24814)
* Allow us to run our unit test on differents jquery version
* Run karma tests in parallel.
* Update typography docs (#24863)
* closes #24450
* Rewrite custom form check backgrounds (#24697)
* Rewrite custom form check backgrounds
Previously, this was all just a background-color and background-image. When we restored the gradients though, we had two background-images competing on the same element, causing rendering glitches. This refactors that code, creating a mixin to simplify things, so we can we easily use two background-images (SVG icon and gradient) when -gradients is set to true.
Fixes #24598
* restore default vars
* Revamp custom check and radio backgrounds
Instead of applying multiple background-image's to the same element, we're adding a new ::before pseudo-element to layer the background-images. Gradients go on the .custom-control-indicator while their icons go on the ::before element. This allows us to shave some bytes from when we compile and we previously needed to redeclare the background-image for the icon if you changed the gradient.
* remove now unused mixin
* mention change in migration docs
* lets the centered modal have any height (#24803)
* Custom select updates (#24699)
* Add support for size attribute on custom selects
* Add large custom select, document it and the small variant
* fix custom select focus state
* fix custom file input focus styles
* remove empty line
* Update package.json. (#24582)
1. Use the same jQuery version in jspm
2. Update the files to only include the source and dist folders
* Use Jekyll's `smartify` filter when possible. (#24866)
* Darken outline hover color to match default button hover (#24150)
* Fix Issue #24144
Alter button-outline-variant mixin to darken hover and active background in same fashion as filled button.
* Fix Issue #24144
Filled button on hover should utilize the same color-yiq mixin so that theme buttons match
* default values, fix mixin
* rename it
* document it
* add migration note
* fixes #24728
* Remove unused CSS. (#24872)
* tab.js: do not remove fade class if there's no initial active pane
* Restore currently unused variables (#24891)
* Replace lint-vars.sh with a Node.js script. (#24860)
Also, include it in the `css` npm script since it's instant.
* Fix docs horizontal scrollbar (#24878)
* Fix docs horizontal scrollbar in Components > Modal
* Add overflow to docs example class
* Drop the handleUpdate() variant
While I understand the variant covers the "get a particular plugin instance" case from http://getbootstrap.com/docs/4.0/getting-started/javascript/#programmatic-api it seems weird that we do it here but not everywhere else in the docs (randomly checking other pages, we seem to stick to the documented methods as written on those pages). As this isn't properly explained as is, and as it adds nothing (more of a preference for authors), it would be easier to just drop the variant and stick with the documented method as outlined later on in the same page (avoids having to go off on a "why should you use this instead of that" tangent here).
* Combine path and remove variable used in one place. (#24873)
* Update devDependencies and gems. (#24876)
* Override padding on radio input label (#24899)
We could tell folks to nix the class, we could tell them to override it, or we could add another modifier of some kind to address this. None of them seem particularly useful, but the padding override feels the most approachable and clearly documentable. Added this here to close #24844.
* Update README.md (#24912)
* Work around Travis failures.
Note that we should revert this when the issue is fixed.
* Revert the Travis workaround. (#24926)
The issue has been fixed.
* add .col-form-legend-lg and .col-form-legend-sm classes
* document .col-form-legend-{size}
* trash .col-form-legend completely
One class fits all
* Update forms.md
* consolidate copy
* property order
2017-12-02 20:51:38 +01:00
Be sure to use `.col-form-label-sm` or `.col-form-label-lg` to your `<label>` s or `<legend>` s to correctly follow the size of `.form-control-lg` and `.form-control-sm` .
2017-10-18 19:11:35 +02:00
{% example html %}
< form >
< div class = "form-group row" >
< label for = "colFormLabelSm" class = "col-sm-2 col-form-label col-form-label-sm" > Email< / label >
< div class = "col-sm-10" >
< input type = "email" class = "form-control form-control-sm" id = "colFormLabelSm" placeholder = "col-form-label-sm" >
< / div >
< / div >
< div class = "form-group row" >
< label for = "colFormLabel" class = "col-sm-2 col-form-label" > Email< / label >
< div class = "col-sm-10" >
< input type = "email" class = "form-control" id = "colFormLabel" placeholder = "col-form-label" >
< / div >
< / div >
< div class = "form-group row" >
< label for = "colFormLabelLg" class = "col-sm-2 col-form-label col-form-label-lg" > Email< / label >
< div class = "col-sm-10" >
< input type = "email" class = "form-control form-control-lg" id = "colFormLabelLg" placeholder = "col-form-label-lg" >
< / div >
< / div >
< / form >
2017-06-14 07:11:44 +02:00
{% endexample %}
#### Column sizing
As shown in the previous examples, our grid system allows you to place any number of `.col` s within a `.row` or `.form-row` . They'll split the available width equally between them. You may also pick a subset of your columns to take up more or less space, while the remaining `.col` s equally split the rest, with specific column classes like `.col-7` .
{% example html %}
< form >
< div class = "form-row" >
< div class = "col-7" >
< input type = "text" class = "form-control" placeholder = "City" >
< / div >
< div class = "col" >
< input type = "text" class = "form-control" placeholder = "State" >
< / div >
< div class = "col" >
< input type = "text" class = "form-control" placeholder = "Zip" >
< / div >
< / div >
< / form >
{% endexample html %}
#### Auto-sizing
The example below uses a flexbox utility to vertically center the contents and changes `.col` to `.col-auto` so that your columns only take up as much space as needed. Put another way, the column sizes itself based on the contents.
{% example html %}
< form >
< div class = "form-row align-items-center" >
< div class = "col-auto" >
< label class = "sr-only" for = "inlineFormInput" > Name< / label >
2017-10-27 14:55:07 +02:00
< input type = "text" class = "form-control mb-2" id = "inlineFormInput" placeholder = "Jane Doe" >
2017-06-14 07:11:44 +02:00
< / div >
2017-05-27 05:15:30 +02:00
< div class = "col-auto" >
< label class = "sr-only" for = "inlineFormInputGroup" > Username< / label >
2017-10-27 14:55:07 +02:00
< div class = "input-group mb-2" >
2017-12-23 00:29:49 +01:00
< div class = "input-group-prepend" >
< div class = "input-group-text" > @< / div >
< / div >
2017-05-27 05:15:30 +02:00
< input type = "text" class = "form-control" id = "inlineFormInputGroup" placeholder = "Username" >
< / div >
< / div >
< div class = "col-auto" >
2017-10-27 14:55:07 +02:00
< div class = "form-check mb-2" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "autoSizingCheck" >
< label class = "form-check-label" for = "autoSizingCheck" >
Remember me
2017-05-27 05:15:30 +02:00
< / label >
< / div >
< / div >
< div class = "col-auto" >
2017-10-27 14:55:07 +02:00
< button type = "submit" class = "btn btn-primary mb-2" > Submit< / button >
2017-05-27 05:15:30 +02:00
< / div >
< / div >
< / form >
{% endexample %}
2017-06-14 07:11:44 +02:00
You can then remix that once again with size-specific column classes.
2017-05-27 05:15:30 +02:00
{% example html %}
< form >
2017-06-14 07:11:44 +02:00
< div class = "form-row align-items-center" >
2017-12-23 01:13:01 +01:00
< div class = "col-sm-3 my-1" >
2017-06-15 11:28:48 +02:00
< label class = "sr-only" for = "inlineFormInputName" > Name< / label >
2017-12-23 01:13:01 +01:00
< input type = "text" class = "form-control" id = "inlineFormInputName" placeholder = "Jane Doe" >
2017-05-27 05:15:30 +02:00
< / div >
2017-12-23 01:13:01 +01:00
< div class = "col-sm-3 my-1" >
2017-06-15 11:28:48 +02:00
< label class = "sr-only" for = "inlineFormInputGroupUsername" > Username< / label >
2017-12-23 01:13:01 +01:00
< div class = "input-group" >
2017-12-23 00:29:49 +01:00
< div class = "input-group-prepend" >
< div class = "input-group-text" > @< / div >
< / div >
2017-06-15 11:28:48 +02:00
< input type = "text" class = "form-control" id = "inlineFormInputGroupUsername" placeholder = "Username" >
2017-05-27 05:15:30 +02:00
< / div >
< / div >
2017-12-23 01:13:01 +01:00
< div class = "col-auto my-1" >
< div class = "form-check" >
< input class = "form-check-input" type = "checkbox" id = "autoSizingCheck2" >
< label class = "form-check-label" for = "autoSizingCheck2" >
Remember me
2017-05-27 05:15:30 +02:00
< / label >
< / div >
< / div >
2017-12-23 01:13:01 +01:00
< div class = "col-auto my-1" >
2017-05-27 05:15:30 +02:00
< button type = "submit" class = "btn btn-primary" > Submit< / button >
< / div >
< / div >
< / form >
{% endexample %}
2017-06-14 07:11:44 +02:00
And of course [custom form controls ](#custom-forms ) are supported.
2017-05-27 06:54:35 +02:00
{% example html %}
< form >
2017-06-14 07:11:44 +02:00
< div class = "form-row align-items-center" >
2017-12-23 01:13:01 +01:00
< div class = "col-auto my-1" >
2017-05-27 06:54:35 +02:00
< label class = "mr-sm-2" for = "inlineFormCustomSelect" > Preference< / label >
2017-12-23 01:13:01 +01:00
< select class = "custom-select mr-sm-2" id = "inlineFormCustomSelect" >
2017-05-27 06:54:35 +02:00
< option selected > Choose...< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
< / div >
2017-12-23 01:13:01 +01:00
< div class = "col-auto my-1" >
< div class = "custom-control custom-checkbox mr-sm-2" >
< input type = "checkbox" class = "custom-control-input" id = "customControlAutosizing" >
< label class = "custom-control-label" for = "customControlAutosizing" > Remember my preference< / label >
< / div >
2017-05-27 06:54:35 +02:00
< / div >
2017-12-23 01:13:01 +01:00
< div class = "col-auto my-1" >
< button type = "submit" class = "btn btn-primary" > Submit< / button >
2017-05-27 06:54:35 +02:00
< / div >
< / div >
< / form >
{% endexample %}
2015-04-18 01:02:41 +02:00
### Inline forms
2016-11-27 01:55:18 +01:00
Use the `.form-inline` class to display a series of labels, form controls, and buttons on a single horizontal row. Form controls within inline forms vary slightly from their default states.
2015-04-18 01:02:41 +02:00
2017-07-02 04:33:27 +02:00
- Controls are `display: flex` , collapsing any HTML white space and allowing you to provide alignment control with [spacing ]({{ site.baseurl }}/docs/{{ site.docs_version }}/utilities/spacing/ ) and [flexbox ]({{ site.baseurl }}/docs/{{ site.docs_version }}/utilities/flex/ ) utilities.
2016-11-27 01:55:18 +01:00
- Controls and input groups receive `width: auto` to override the Bootstrap default `width: 100%` .
- Controls **only appear inline in viewports that are at least 576px wide** to account for narrow viewports on mobile devices.
2014-07-12 07:34:47 +02:00
2017-05-29 20:38:06 +02:00
You may need to manually address the width and alignment of individual form controls with [spacing utilities ]({{ site.baseurl }}/docs/{{ site.docs_version }}/utilities/spacing/ ) (as shown below). Lastly, be sure to always include a `<label>` with each form control, even if you need to hide it from non-screenreader visitors with `.sr-only` .
2015-01-20 01:00:56 +01:00
{% example html %}
2015-04-18 01:02:41 +02:00
< form class = "form-inline" >
2017-06-15 11:28:48 +02:00
< label class = "sr-only" for = "inlineFormInputName2" > Name< / label >
2017-10-27 14:55:07 +02:00
< input type = "text" class = "form-control mb-2 mr-sm-2" id = "inlineFormInputName2" placeholder = "Jane Doe" >
2015-01-20 01:00:56 +01:00
2017-06-15 11:28:48 +02:00
< label class = "sr-only" for = "inlineFormInputGroupUsername2" > Username< / label >
2017-10-27 14:55:07 +02:00
< div class = "input-group mb-2 mr-sm-2" >
2017-12-23 00:29:49 +01:00
< div class = "input-group-prepend" >
< div class = "input-group-text" > @< / div >
< / div >
2017-06-15 11:28:48 +02:00
< input type = "text" class = "form-control" id = "inlineFormInputGroupUsername2" placeholder = "Username" >
2014-03-17 03:03:53 +01:00
< / div >
2016-11-27 01:55:18 +01:00
2017-10-27 14:55:07 +02:00
< div class = "form-check mb-2 mr-sm-2" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "inlineFormCheck" >
< label class = "form-check-label" for = "inlineFormCheck" >
Remember me
2014-03-17 03:03:53 +01:00
< / label >
< / div >
2016-11-27 01:55:18 +01:00
2017-10-27 14:55:07 +02:00
< button type = "submit" class = "btn btn-primary mb-2" > Submit< / button >
2014-12-01 05:17:45 +01:00
< / form >
{% endexample %}
2016-11-27 01:55:18 +01:00
Custom form controls and selects are also supported.
2014-12-01 05:17:45 +01:00
{% example html %}
< form class = "form-inline" >
2017-12-23 01:13:01 +01:00
< label class = "my-1 mr-2" for = "inlineFormCustomSelectPref" > Preference< / label >
< select class = "custom-select my-1 mr-sm-2" id = "inlineFormCustomSelectPref" >
2016-11-27 01:55:18 +01:00
< option selected > Choose...< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-checkbox my-1 mr-sm-2" >
< input type = "checkbox" class = "custom-control-input" id = "customControlInline" >
< label class = "custom-control-label" for = "customControlInline" > Remember my preference< / label >
< / div >
2016-11-27 01:55:18 +01:00
2017-12-23 01:13:01 +01:00
< button type = "submit" class = "btn btn-primary my-1" > Submit< / button >
2014-03-17 03:03:53 +01:00
< / form >
2014-07-12 07:34:47 +02:00
{% endexample %}
2014-03-17 03:03:53 +01:00
2016-02-19 15:57:26 +01:00
{% callout warning %}
2016-05-09 07:52:58 +02:00
#### Alternatives to hidden labels
Assistive technologies such as screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the `.sr-only` class. There are further alternative methods of providing a label for assistive technologies, such as the `aria-label` , `aria-labelledby` or `title` attribute. If none of these are present, assistive technologies may resort to using the `placeholder` attribute, if present, but note that use of `placeholder` as a replacement for other labelling methods is not advised.
{% endcallout %}
2016-02-19 15:57:26 +01:00
2017-06-14 07:11:44 +02:00
## Help text
2014-07-12 07:34:47 +02:00
2017-06-14 07:11:44 +02:00
Block-level help text in forms can be created using `.form-text` (previously known as `.help-block` in v3). Inline help text can be flexibly implemented using any inline HTML element and utility classes like `.text-muted` .
2014-03-26 07:00:47 +01:00
2017-06-14 07:11:44 +02:00
{% callout warning %}
##### Associating help text with form controls
2014-03-17 03:03:53 +01:00
2017-06-14 07:11:44 +02:00
Help text should be explicitly associated with the form control it relates to using the `aria-describedby` attribute. This will ensure that assistive technologies—such as screen readers—will announce this help text when the user focuses or enters the control.
{% endcallout %}
2014-10-27 06:31:59 +01:00
2017-06-14 07:11:44 +02:00
Help text below inputs can be styled with `.form-text` . This class includes `display: block` and adds some top margin for easy spacing from the inputs above.
2014-10-27 06:31:59 +01:00
{% example html %}
2017-06-14 07:11:44 +02:00
< label for = "inputPassword5" > Password< / label >
< input type = "password" id = "inputPassword5" class = "form-control" aria-describedby = "passwordHelpBlock" >
< small id = "passwordHelpBlock" class = "form-text text-muted" >
Your password must be 8-20 characters long, contain letters and numbers, and must not contain spaces, special characters, or emoji.
< / small >
2014-10-27 06:31:59 +01:00
{% endexample %}
2017-06-14 07:11:44 +02:00
Inline text can use any typical inline HTML element (be it a `<small>` , `<span>` , or something else) with nothing more than a utility class.
2014-03-17 03:03:53 +01:00
2014-08-03 03:30:59 +02:00
{% example html %}
2014-12-01 05:17:45 +01:00
< form class = "form-inline" >
2014-08-03 03:30:59 +02:00
< div class = "form-group" >
2017-06-14 07:11:44 +02:00
< label for = "inputPassword6" > Password< / label >
< input type = "password" id = "inputPassword6" class = "form-control mx-sm-3" aria-describedby = "passwordHelpInline" >
< small id = "passwordHelpInline" class = "text-muted" >
Must be 8-20 characters long.
< / small >
2014-08-03 03:30:59 +02:00
< / div >
< / form >
{% endexample %}
2017-06-14 07:11:44 +02:00
## Disabled forms
2014-03-17 03:03:53 +01:00
2017-04-28 00:57:10 +02:00
Add the `disabled` boolean attribute on an input to prevent user interactions and make it appear lighter.
2014-03-17 03:03:53 +01:00
{% highlight html %}
2014-07-12 07:34:47 +02:00
< input class = "form-control" id = "disabledInput" type = "text" placeholder = "Disabled input here..." disabled >
{% endhighlight %}
Add the `disabled` attribute to a `<fieldset>` to disable all the controls within.
{% example html %}
2014-12-01 05:17:45 +01:00
< form >
2014-03-17 03:03:53 +01:00
< fieldset disabled >
< div class = "form-group" >
< label for = "disabledTextInput" > Disabled input< / label >
< input type = "text" id = "disabledTextInput" class = "form-control" placeholder = "Disabled input" >
< / div >
< div class = "form-group" >
< label for = "disabledSelect" > Disabled select menu< / label >
< select id = "disabledSelect" class = "form-control" >
< option > Disabled select< / option >
< / select >
< / div >
2017-09-05 00:31:18 +02:00
< div class = "form-check" >
2017-12-23 01:13:01 +01:00
< input class = "form-check-input" type = "checkbox" id = "disabledFieldsetCheck" disabled >
< label class = "form-check-label" for = "disabledFieldsetCheck" >
Can't check this
2014-03-17 03:03:53 +01:00
< / label >
< / div >
< button type = "submit" class = "btn btn-primary" > Submit< / button >
< / fieldset >
< / form >
2014-07-12 07:34:47 +02:00
{% endexample %}
2014-03-17 03:03:53 +01:00
2015-04-17 01:56:40 +02:00
{% callout warning %}
2017-05-29 04:48:44 +02:00
#### Caveat with anchors
2014-03-17 03:03:53 +01:00
2017-09-04 14:31:48 +02:00
By default, browsers will treat all native form controls (`< input > `, `<select>` and `<button>` elements) inside a `<fieldset disabled>` as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes `<a ... class="btn btn-*">` elements, these will only be given a style of `pointer-events: none` . As noted in the section about [disabled state for buttons ]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/buttons/#disabled-state ) (and specifically in the sub-section for anchor elements), this CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 10, and won't prevent keyboard users from being able to focus or activate these links. So to be safe, use custom JavaScript to disable such links.
2015-04-17 01:56:40 +02:00
{% endcallout %}
{% callout danger %}
#### Cross-browser compatibility
While Bootstrap will apply these styles in all browsers, Internet Explorer 11 and below don't fully support the `disabled` attribute on a `<fieldset>` . Use custom JavaScript to disable the fieldset in these browsers.
{% endcallout %}
2014-07-12 07:34:47 +02:00
## Validation
2014-03-17 03:03:53 +01:00
2017-09-26 14:24:14 +02:00
Provide valuable, actionable feedback to your users with HTML5 form validation– [available in all our supported browsers](https://caniuse.com/#feat=form-validation). Choose from the browser default validation feedback, or implement custom messages with our built-in classes and starter JavaScript.
2017-06-06 05:21:08 +02:00
2017-06-06 20:25:54 +02:00
{% callout warning %}
2017-06-11 01:30:35 +02:00
We **highly recommend** custom validation styles as native browser defaults are not announced to screen readers.
2017-06-06 20:25:54 +02:00
{% endcallout %}
2016-10-29 01:36:09 +02:00
### How it works
2017-06-12 01:24:20 +02:00
Here's how form validation works with Bootstrap:
2017-06-06 05:21:08 +02:00
2017-06-12 01:24:20 +02:00
- HTML form validation is applied via CSS's two pseudo-classes, `:invalid` and `:valid` . It applies to `<input>` , `<select>` , and `<textarea>` elements.
2017-06-06 08:00:14 +02:00
- Bootstrap scopes the `:invalid` and `:valid` styles to parent `.was-validated` class, usually applied to the `<form>` . Otherwise, any required field without a value shows up as invalid on page load. This way, you may choose when to activate them (typically after form submission is attempted).
2017-06-12 01:24:20 +02:00
- As a fallback, `.is-invalid` and `.is-valid` classes may be used instead of the pseudo-classes for [server side validation ](#server-side ). They do not require a `.was-validated` parent class.
2017-08-06 11:34:10 +02:00
- Due to constraints in how CSS works, we cannot (at present) apply styles to a `<label>` that comes before a form control in the DOM without the help of custom JavaScript.
2017-06-06 05:21:08 +02:00
- All modern browsers support the [constraint validation API ](https://www.w3.org/TR/html5/forms.html#the-constraint-validation-api ), a series of JavaScript methods for validating form controls.
2017-09-01 14:01:17 +02:00
- Feedback messages may utilize the [browser defaults ](#browser-defaults ) (different for each browser, and unstylable via CSS) or our custom feedback styles with additional HTML and CSS.
2017-06-06 05:21:08 +02:00
- You may provide custom validity messages with `setCustomValidity` in JavaScript.
2017-06-12 01:24:20 +02:00
With that in mind, consider the following demos for our custom form validation styles, optional server side classes, and browser defaults.
2017-06-06 08:00:14 +02:00
### Custom styles
2017-06-06 20:26:08 +02:00
For custom Bootstrap form validation messages, you'll need to add the `novalidate` boolean attribute to your `<form>` . This disables the browser default feedback tooltips, but still provides access to the form validation APIs in JavaScript. Try to submit the form below; our JavaScript will intercept the submit button and relay feedback to you.
2017-06-06 08:00:14 +02:00
2017-06-11 01:31:14 +02:00
When attempting to submit, you'll see the `:invalid` and `:valid` styles applied to your form controls.
2017-06-06 08:00:14 +02:00
{% example html %}
2017-10-30 00:03:13 +01:00
< form id = "needs-validation" novalidate >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
< div class = "col-md-4 mb-3" >
2017-06-06 08:00:14 +02:00
< label for = "validationCustom01" > First name< / label >
< input type = "text" class = "form-control" id = "validationCustom01" placeholder = "First name" value = "Mark" required >
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
2017-06-06 08:00:14 +02:00
< label for = "validationCustom02" > Last name< / label >
< input type = "text" class = "form-control" id = "validationCustom02" placeholder = "Last name" value = "Otto" required >
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
< label for = "validationCustomUsername" > Username< / label >
< div class = "input-group" >
< div class = "input-group-prepend" >
< span class = "input-group-text" id = "inputGroupPrepend" > @< / span >
< / div >
< input type = "text" class = "form-control" id = "validationCustomUsername" placeholder = "Username" aria-describedby = "inputGroupPrepend" required >
< div class = "invalid-feedback" >
Please choose a username.
< / div >
< / div >
< / div >
2017-06-06 08:00:14 +02:00
< / div >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
2017-06-06 08:00:14 +02:00
< div class = "col-md-6 mb-3" >
< label for = "validationCustom03" > City< / label >
< input type = "text" class = "form-control" id = "validationCustom03" placeholder = "City" required >
< div class = "invalid-feedback" >
Please provide a valid city.
< / div >
< / div >
< div class = "col-md-3 mb-3" >
< label for = "validationCustom04" > State< / label >
< input type = "text" class = "form-control" id = "validationCustom04" placeholder = "State" required >
< div class = "invalid-feedback" >
Please provide a valid state.
< / div >
< / div >
< div class = "col-md-3 mb-3" >
< label for = "validationCustom05" > Zip< / label >
< input type = "text" class = "form-control" id = "validationCustom05" placeholder = "Zip" required >
< div class = "invalid-feedback" >
Please provide a valid zip.
< / div >
< / div >
< / div >
< button class = "btn btn-primary" type = "submit" > Submit form< / button >
< / form >
< script >
2017-06-06 20:26:08 +02:00
// Example starter JavaScript for disabling form submissions if there are invalid fields
2017-06-06 08:00:14 +02:00
(function() {
2017-09-28 16:25:28 +02:00
'use strict';
window.addEventListener('load', function() {
var form = document.getElementById('needs-validation');
form.addEventListener('submit', function(event) {
if (form.checkValidity() === false) {
2017-06-06 08:00:14 +02:00
event.preventDefault();
event.stopPropagation();
}
2017-09-28 16:25:28 +02:00
form.classList.add('was-validated');
2017-06-06 08:00:14 +02:00
}, false);
}, false);
2017-09-28 16:25:28 +02:00
})();
2017-06-06 08:00:14 +02:00
< / script >
{% endexample %}
### Browser defaults
2017-06-06 20:26:24 +02:00
Not interested in custom validation feedback messages or writing JavaScript to change form behaviors? All good, you can use the browser defaults. Try submitting the form below. Depending on your browser and OS, you'll see a slightly different style of feedback.
While these feedback styles cannot be styled with CSS, you can still customize the feedback text through JavaScript.
2017-06-06 08:00:14 +02:00
{% example html %}
< form >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
< div class = "col-md-4 mb-3" >
2017-06-11 01:31:36 +02:00
< label for = "validationDefault01" > First name< / label >
< input type = "text" class = "form-control" id = "validationDefault01" placeholder = "First name" value = "Mark" required >
2017-06-06 08:00:14 +02:00
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
2017-06-11 01:31:36 +02:00
< label for = "validationDefault02" > Last name< / label >
< input type = "text" class = "form-control" id = "validationDefault02" placeholder = "Last name" value = "Otto" required >
2017-06-06 08:00:14 +02:00
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
< label for = "validationDefaultUsername" > Username< / label >
< div class = "input-group" >
< div class = "input-group-prepend" >
< span class = "input-group-text" id = "inputGroupPrepend2" > @< / span >
< / div >
< input type = "text" class = "form-control" id = "validationDefaultUsername" placeholder = "Username" aria-describedby = "inputGroupPrepend2" required >
< / div >
< / div >
2017-06-06 08:00:14 +02:00
< / div >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
2017-06-11 01:31:36 +02:00
< div class = "col-md-6 mb-3" >
< label for = "validationDefault03" > City< / label >
< input type = "text" class = "form-control" id = "validationDefault03" placeholder = "City" required >
< / div >
< div class = "col-md-3 mb-3" >
< label for = "validationDefault04" > State< / label >
< input type = "text" class = "form-control" id = "validationDefault04" placeholder = "State" required >
< / div >
< div class = "col-md-3 mb-3" >
< label for = "validationDefault05" > Zip< / label >
< input type = "text" class = "form-control" id = "validationDefault05" placeholder = "Zip" required >
< / div >
< / div >
< button class = "btn btn-primary" type = "submit" > Submit form< / button >
< / form >
{% endexample %}
2017-06-06 08:00:14 +02:00
2017-06-11 01:31:27 +02:00
### Server side
We recommend using client side validation, but in case you require server side, you can indicate invalid and valid form fields with `.is-invalid` and `.is-valid` . Note that `.invalid-feedback` is also supported with these classes.
{% example html %}
< form >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
< div class = "col-md-4 mb-3" >
2017-06-11 01:31:27 +02:00
< label for = "validationServer01" > First name< / label >
< input type = "text" class = "form-control is-valid" id = "validationServer01" placeholder = "First name" value = "Mark" required >
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
2017-06-11 01:31:27 +02:00
< label for = "validationServer02" > Last name< / label >
< input type = "text" class = "form-control is-valid" id = "validationServer02" placeholder = "Last name" value = "Otto" required >
< / div >
2017-12-23 00:29:49 +01:00
< div class = "col-md-4 mb-3" >
< label for = "validationServerUsername" > Username< / label >
< div class = "input-group" >
< div class = "input-group-prepend" >
< span class = "input-group-text" id = "inputGroupPrepend3" > @< / span >
< / div >
< input type = "text" class = "form-control is-invalid" id = "validationServerUsername" placeholder = "Username" aria-describedby = "inputGroupPrepend3" required >
< div class = "invalid-feedback" >
Please choose a username.
< / div >
< / div >
< / div >
2017-06-11 01:31:27 +02:00
< / div >
2017-12-23 00:29:49 +01:00
< div class = "form-row" >
2017-06-11 01:31:27 +02:00
< div class = "col-md-6 mb-3" >
< label for = "validationServer03" > City< / label >
< input type = "text" class = "form-control is-invalid" id = "validationServer03" placeholder = "City" required >
< div class = "invalid-feedback" >
Please provide a valid city.
< / div >
2017-06-06 08:00:14 +02:00
< / div >
< div class = "col-md-3 mb-3" >
2017-06-11 01:31:27 +02:00
< label for = "validationServer04" > State< / label >
< input type = "text" class = "form-control is-invalid" id = "validationServer04" placeholder = "State" required >
< div class = "invalid-feedback" >
Please provide a valid state.
< / div >
2017-06-06 08:00:14 +02:00
< / div >
2017-06-11 01:31:27 +02:00
< div class = "col-md-3 mb-3" >
< label for = "validationServer05" > Zip< / label >
< input type = "text" class = "form-control is-invalid" id = "validationServer05" placeholder = "Zip" required >
< div class = "invalid-feedback" >
Please provide a valid zip.
< / div >
2017-06-06 08:00:14 +02:00
< / div >
< / div >
< button class = "btn btn-primary" type = "submit" > Submit form< / button >
< / form >
{% endexample %}
### Supported elements
Our example forms show native textual `<input>` s above, but form validation styles are available for our custom form controls, too.
{% example html %}
< form class = "was-validated" >
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-checkbox" >
< input type = "checkbox" class = "custom-control-input" id = "customControlValidation1" required >
< label class = "custom-control-label" for = "customControlValidation1" > Check this custom checkbox< / label >
< / div >
2017-06-06 08:00:14 +02:00
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-radio" >
< input type = "radio" class = "custom-control-input" id = "customControlValidation2" name = "radio-stacked" required >
< label class = "custom-control-label" for = "customControlValidation2" > Toggle this custom radio< / label >
< / div >
< div class = "custom-control custom-radio" >
< input type = "radio" class = "custom-control-input" id = "customControlValidation3" name = "radio-stacked" required >
< label class = "custom-control-label" for = "customControlValidation3" > Or toggle this other custom radio< / label >
2017-06-06 08:00:14 +02:00
< / div >
< select class = "custom-select d-block my-3" required >
< option value = "" > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
< label class = "custom-file" >
< input type = "file" id = "file" class = "custom-file-input" required >
< span class = "custom-file-control" > < / span >
< / label >
< / form >
{% endexample %}
2016-02-07 03:16:37 +01:00
2015-04-18 01:50:02 +02:00
## Custom forms
2015-12-06 21:08:01 +01:00
For even more customization and cross browser consistency, use our completely custom form elements to replace the browser defaults. They're built on top of semantic and accessible markup, so they're solid replacements for any default form control.
2015-04-18 01:50:02 +02:00
### Checkboxes and radios
2017-12-23 01:13:01 +01:00
Each checkbox and radio is wrapped in a `<div>` with a sibling `<span>` to create our custom control and a `<label>` for the accompanying text. Structurally, this is the same approach as our default `.form-check` .
2015-04-18 01:50:02 +02:00
2017-12-23 01:13:01 +01:00
We use the sibling selector (`~`) for all our `<input>` states—like `:checked` —to properly style our custom form indicator. When combined with the `.custom-control-label` class, we can also style the text for each item based on the `<input>` 's state.
2015-04-18 01:50:02 +02:00
2017-12-23 01:13:01 +01:00
We hide the default `<input>` with `opacity` and use the `.custom-control-label` to build a new custom form indicator in its place with `::before` and `::after` . Unfortunately we can't build a custom one from just the `<input>` because CSS's `content` doesn't work on that element.
2015-04-18 01:50:02 +02:00
2015-08-26 21:11:44 +02:00
In the checked states, we use **base64 embedded SVG icons** from [Open Iconic ](https://useiconic.com/open ). This provides us the best control for styling and positioning across browsers and devices.
2015-04-18 01:50:02 +02:00
#### Checkboxes
{% example html %}
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-checkbox" >
< input type = "checkbox" class = "custom-control-input" id = "customCheck1" >
< label class = "custom-control-label" for = "customCheck1" > Check this custom checkbox< / label >
< / div >
2015-04-18 01:50:02 +02:00
{% endexample %}
2015-08-08 23:15:09 +02:00
Custom checkboxes can also utilize the `:indeterminate` pseudo class when manually set via JavaScript (there is no available HTML attribute for specifying it).
2015-04-18 01:50:02 +02:00
< div class = "bd-example bd-example-indeterminate" >
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-checkbox" >
< input type = "checkbox" class = "custom-control-input" id = "customCheck2" >
< label class = "custom-control-label" for = "customCheck2" > Check this custom checkbox< / label >
< / div >
2015-04-18 01:50:02 +02:00
< / div >
2016-01-06 08:26:36 +01:00
If you're using jQuery, something like this should suffice:
2015-04-18 01:50:02 +02:00
{% highlight js %}
$('.your-checkbox').prop('indeterminate', true)
{% endhighlight %}
#### Radios
{% example html %}
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-radio" >
< input type = "radio" id = "customRadio1" name = "customRadio" class = "custom-control-input" >
< label class = "custom-control-label" for = "customRadio1" > Toggle this custom radio< / label >
< / div >
< div class = "custom-control custom-radio" >
< input type = "radio" id = "customRadio2" name = "customRadio" class = "custom-control-input" >
< label class = "custom-control-label" for = "customRadio2" > Or toggle this other custom radio< / label >
< / div >
2015-04-18 01:50:02 +02:00
{% endexample %}
2017-12-23 01:13:01 +01:00
#### Inline
2016-01-06 08:26:36 +01:00
{% example html %}
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-radio custom-control-inline" >
< input type = "radio" id = "customRadioInline1" name = "customRadioInline1" class = "custom-control-input" >
< label class = "custom-control-label" for = "customRadioInline1" > Toggle this custom radio< / label >
< / div >
< div class = "custom-control custom-radio custom-control-inline" >
< input type = "radio" id = "customRadioInline2" name = "customRadioInline1" class = "custom-control-input" >
< label class = "custom-control-label" for = "customRadioInline2" > Or toggle this other custom radio< / label >
< / div >
2016-01-06 08:26:36 +01:00
{% endexample %}
2017-12-23 01:13:01 +01:00
#### Disabled
2015-04-18 01:50:02 +02:00
2017-12-23 01:13:01 +01:00
Custom checkboxes and radios can also be disabled. Add the `disabled` boolean attribute to the `<input>` and the custom indicator and label description will be automatically styled.
2015-04-18 01:50:02 +02:00
{% example html %}
2017-12-23 01:13:01 +01:00
< div class = "custom-control custom-checkbox" >
< input type = "checkbox" class = "custom-control-input" id = "customCheckDisabled" disabled >
< label class = "custom-control-label" for = "customCheckDisabled" > Check this custom checkbox< / label >
< / div >
< div class = "custom-control custom-radio" >
< input type = "radio" id = "radio3" name = "radioDisabled" id = "customRadioDisabled" class = "custom-control-input" disabled >
< label class = "custom-control-label" for = "customRadioDisabled" > Toggle this custom radio< / label >
2015-04-18 01:50:02 +02:00
< / div >
{% endexample %}
### Select menu
2016-01-06 08:34:51 +01:00
Custom `<select>` menus need only a custom class, `.custom-select` to trigger the custom styles.
2015-04-18 01:50:02 +02:00
{% example html %}
2016-01-06 08:34:51 +01:00
< select class = "custom-select" >
2015-08-19 04:26:18 +02:00
< option selected > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
2017-11-24 23:29:59 +01:00
< option value = "3" > Three< / option >
< / select >
{% endexample %}
You may also choose from small and large custom selects to match our similarly sized text inputs.
{% example html %}
< select class = "custom-select custom-select-lg" >
< option selected > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
< select class = "custom-select custom-select-sm" >
< option selected > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
{% endexample %}
The `multiple` attribute is also supported:
{% example html %}
< select class = "custom-select" multiple >
< option selected > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
< option value = "3" > Three< / option >
< / select >
{% endexample %}
As is the `size` attribute:
{% example html %}
< select class = "custom-select" size = "3" >
< option selected > Open this select menu< / option >
< option value = "1" > One< / option >
< option value = "2" > Two< / option >
2015-08-19 04:26:18 +02:00
< option value = "3" > Three< / option >
< / select >
2015-04-18 01:50:02 +02:00
{% endexample %}
### File browser
2016-01-06 08:45:44 +01:00
The file input is the most gnarly of the bunch and require additional JavaScript if you'd like to hook them up with functional *Choose file...* and selected file name text.
2015-04-18 01:50:02 +02:00
{% example html %}
2016-01-06 08:45:44 +01:00
< label class = "custom-file" >
2017-06-15 11:28:48 +02:00
< input type = "file" id = "file2" class = "custom-file-input" >
2016-01-06 08:45:44 +01:00
< span class = "custom-file-control" > < / span >
2015-04-18 01:50:02 +02:00
< / label >
{% endexample %}
2016-01-06 08:45:44 +01:00
Here's how it works:
2015-04-18 01:50:02 +02:00
- We wrap the `<input>` in a `<label>` so the custom control properly triggers the file browser.
- We hide the default file `<input>` via `opacity` .
2017-09-08 02:06:02 +02:00
- We use `::after` to generate a custom background and directive (*Choose file...*).
- We use `::before` to generate and position the *Browse* button.
2015-04-18 01:50:02 +02:00
- We declare a `height` on the `<input>` for proper spacing for surrounding content.
In other words, it's an entirely custom element, all generated via CSS.
2016-01-26 22:19:03 +01:00
#### Translating or customizing the strings
The [`:lang()` pseudo-class ](https://developer.mozilla.org/en-US/docs/Web/CSS/:lang ) is used to allow for easy translation of the "Browse" and "Choose file..." text into other languages. Simply override or add entries to the `$custom-file-text` SCSS variable with the relevant [language tag ](https://en.wikipedia.org/wiki/IETF_language_tag ) and localized strings. The English strings can be customized the same way. For example, here's how one might add a Spanish translation (Spanish's language code is `es` ):
{% highlight scss %}
$custom-file-text: (
placeholder: (
en: "Choose file...",
es: "Seleccionar archivo..."
),
button-label: (
en: "Browse",
es: "Navegar"
)
);
{% endhighlight %}
You'll need to set the language of your document (or subtree thereof) correctly in order for the correct text to be shown. This can be done using [the `lang` attribute ](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang ) or the [`Content-Language` HTTP header ](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.12 ), among other methods.