* descriptions for getting started pages * descriptions for layout * add content page descriptions * more descriptions, updates to some existing ones * correct site url * add social stuff to config for twitter cards * add twitter meta tags; use large image for homepage and regular card for all others * add the assets * more site config * more social shiz to partial, remove existing meta for the partial, remove page title from homepage for simpler if statements
8.5 KiB
layout | title | description | group | redirect_from |
---|---|---|---|---|
docs | Buttons | Use Bootstrap's custom button styles for actions in forms, dialogs, and more with support for multiple sizes, states, and more. | components | /components/ |
Use Bootstrap's custom button styles for actions in forms, dialogs, and more. Includes support for a handful of contextual variations, sizes, states, and more.
Contents
- Will be replaced with the ToC, excluding the "Contents" header {:toc}
Examples
Bootstrap includes six predefined button styles, each serving its own semantic purpose.
{% example html %}
Primary
Secondary
Success
Info
Warning
Danger
Link {% endexample %}
{% capture callout-include %}{% include callout-warning-color-assistive-technologies.md %}{% endcapture %} {{ callout-include | markdownify }}
Button tags
The .btn
classes are designed to be used with the <button>
element. However, you can also use these classes on <a>
or <input>
elements (though some browsers may apply a slightly different rendering).
When using button classes on <a>
elements that are used to trigger in-page functionality (like collapsing content), rather than linking to new pages or sections within the current page, these links should be given a role="button"
to appropriately convey their purpose to assistive technologies such as screen readers.
{% example html %} Link Button {% endexample %}
Outline buttons
In need of a button, but not the hefty background colors they bring? Replace the default modifier classes with the .btn-outline-*
ones to remove all background images and colors on any button.
{% example html %} Primary Secondary Success Info Warning Danger {% endexample %}
Sizes
Fancy larger or smaller buttons? Add .btn-lg
or .btn-sm
for additional sizes.
{% example html %} Large button Large button {% endexample %}
{% example html %} Small button Small button {% endexample %}
Create block level buttons—those that span the full width of a parent—by adding .btn-block
.
{% example html %} Block level button Block level button {% endexample %}
Active state
Buttons will appear pressed (with a darker background, darker border, and inset shadow) when active. There's no need to add a class to <button>
s as they use a pseudo-class. However, you can still force the same active appearance with .active
(and include the aria-pressed="true"
attribute) should you need to replicate the state programmatically.
{% example html %} Primary link Link {% endexample %}
Disabled state
Make buttons look inactive by adding the disabled
boolean attribute to any <button>
element.
{% callout info %} Heads up! IE9 and below render disabled buttons with gray, shadowed text that we can't override. {% endcallout %}
{% example html %} Primary button Button {% endexample %}
Disabled buttons using the <a>
element behave a bit different:
<a>
s don't support thedisabled
attribute, so you must add the.disabled
class to make it visually appear disabled.- Some future-friendly styles are included to disable all
pointer-events
on anchor buttons. In browsers which support that property, you won't see the disabled cursor at all. - Disabled buttons should include the
aria-disabled="true"
attribute to indicate the state of the element to assistive technologies.
{% example html %} Primary link Link {% endexample %}
{% callout warning %}
Link functionality caveat
The .disabled
class uses pointer-events: none
to try to disable the link functionality of <a>
s, but that CSS property is not yet standardized. In addition, even in browsers that do support pointer-events: none
, keyboard navigation remains unaffected, meaning that sighted keyboard users and users of assistive technologies will still be able to activate these links. So to be safe, add a tabindex="-1"
attribute on these links (to prevent them from receiving keyboard focus) and use custom JavaScript to disable their functionality.
{% endcallout %}
Button plugin
Do more with buttons. Control button states or create groups of buttons for more components like toolbars.
Toggle states
Add data-toggle="button"
to toggle a button's active
state. If you're pre-toggling a button, you must manually add the .active
class and aria-pressed="true"
to the <button>
.
{% example html %} Single toggle {% endexample %}
Checkbox and radio buttons
Bootstrap's .button
styles can be applied to other elements, such as <label>
s, to provide checkbox or radio style button toggling. Add data-toggle="buttons"
to a .btn-group
containing those modified buttons to enable toggling in their respective styles.
The checked state for these buttons is only updated via click
event on the button. If you use another method to update the input—e.g., with <input type="reset">
or by manually applying the input's checked
property—you'll need to toggle .active
on the <label>
manually.
Note that pre-checked buttons require you to manually add the .active
class to the input's <label>
.
{% example html %}
{% example html %}
Methods
Method | Description |
---|---|
$().button('toggle') |
Toggles push state. Gives the button the appearance that it has been activated. |