4.9 KiB
| layout | title |
|---|---|
| page | Buttons |
Use any of the available button classes to quickly create a styled button.
{% example html %}
{% endexample %}
Sizes
Fancy larger or smaller buttons? Add .btn-lg, .btn-sm, or .btn-xs for additional sizes.
{% example html %} {% endexample %}
{% example html %} {% endexample %}
{% example html %} {% endexample %}
Create block level buttons—those that span the full width of a parent—by adding .btn-block.
{% example html %} {% 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 should you need to replicate the state programmatically.
{% example html %} Primary link Link {% endexample %}
Disabled state
Make buttons look unclickable by adding the disabled boolean attribute to any <button> element.
{% example html %} {% endexample %}
As <a> elements don't support the disabled attribute, you must add the .disabled class to fake it.
{% example html %} Primary link Link {% endexample %}
Cross-browser compatibility
If you add the disabled attribute to a <button>, Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cannot fix.
Link functionality caveat
This class uses pointer-events: none to try to disable the link functionality of <a>s, but that CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11. So to be safe, use custom JavaScript to disable such links.
Context-specific usage
While button classes can be used on <a> and <button> elements, only <button> elements are supported within our nav and navbar components.
Button tags
Use the button classes on an <a>, <button>, or <input> element.
{% example html %} Link {% endexample %}
Cross-browser rendering
As a best practice, we highly recommend using the <button> element whenever possible to ensure matching cross-browser rendering.
Among other things, there's a bug in Firefox <30 that prevents us from setting the line-height of <input>-based buttons, causing them to not exactly match the height of other buttons on Firefox.