7.5 KiB
layout | title | group |
---|---|---|
docs | Forms | material-design |
Bootstrap provides several form control styles, layout options, and custom components for creating a wide variety of forms.
Contents
- Will be replaced with the ToC, excluding the "Contents" header {:toc}
Form controls flavored by Material Design for Bootstrap customizations such as mdb-label-floating
.
{% example html %}
Classes
Below is a complete list of options supported by Material Design for Bootstrap and the classes that customize them. Additional documentation is available for each group.
Classes | Used for | Notes |
---|---|---|
.mdb-form-group
|
Any group of form controls (e.g. combination of label/input). | {% markdown %}This is automatically added by javascript, but if your code is templated, adding `.mdb-form-group` to your form groups or otherwise your groups of controls can reduce rendering churn since the javascript will not add the class after the initial page rendering. This can also demarcate complex label/input combinations inside the same `.form-group`.{% endmarkdown %} |
.mdb-form-group-sm
|
{% markdown %}Added to the `.mdb-form-group`, this will render the combination label/input/help in the smaller variation.{% endmarkdown %} | {% markdown %}{% endmarkdown %} |
.mdb-form-group-lg
|
{% markdown %}Added to the `.mdb-form-group`, this will render the combination label/input/help in the larger variation.{% endmarkdown %} | {% markdown %}{% endmarkdown %} |
.mdb-help
|
Any help text | {% markdown %}Mark any help text next to an input with `.mdb-help` to gain behaviors such as showing upon focus.{% endmarkdown %} |
Form groups
The .mdb-form-group
class is usually added to the .form-group
element. Whereas the .form-group
adds structure to forms by providing margin-bottom
around a label and control pairing,
the only purpose of the .mdb-form-group
is to demarcate Material Design behaviors for a combination of label/input. Focus/hover styling for the label/input is determined based on the .mdb-form-group
.
The .mdb-form-group
is added automatically by javascript through basic discovery of the outer demarcation of the component defined by the Bootstrap standard
markup. If your code is templated, you may want to add .mdb-form-group
to the markup directly to prevent any rendering churn from the javascript determining
and adding the class to the markup. In custom situations, the javascript may not be able to properly resolve the location for the .mdb-form-group
, so in rare or complex cases
you may need to wrap your markup in an .mdb-form-group
to get appropriate focus/hover behavior.
{% example html %}
{% endexample %}Inline forms
Use the .form-inline
class to to display a series of labels, form controls, and buttons on a single horizontal row. Form controls within inline forms behave differently:
- Controls are
display: inline-block
to provide alignment control viavertical-align
andmargin
. - Controls receive
width: auto
to override the Bootstrap defaultwidth: 100%
. - Controls only appear inline in viewports that are at least 768px wide to account for narrow viewports on mobile devices.
Because of this, you may need to manually address the width and alignment of individual form controls. Lastly, as shown below, you should always include a <label>
with each form control.
Visible labels
{% example html %}