• Getting started
  • Introduction
• Layout
  • Breakpoints
  • Containers
  • Grid
• Content
  • Typography
  • Images
• Components
  • Buttons
  • Cards
  • Collapse
  • Dropdowns
  • Forms
  • Input group
  • Modal
  • Navs
  • Navbar
• Helpers
  • Clearfix
  • Colored links
  • Position
  • Visually hidden
• Utilities
  • Borders
  • Colors
  • Display
  • Flex
  • Float
  • Overflow
  • Position
  • Shadows
  • Sizing
  • Spacing
  • Text
  • Vertical align
  • Visibility
• Extend
  • Approach

Buttons

Use Grayshift’s custom button styles for actions in forms, dialogs, and more with support for multiple sizes, states, and more.

Examples

Grayshift includes several predefined button styles, each serving its own semantic purpose, with a few extras thrown in for more control.

<button class="btn btn-primary" type="button">Primary</button>
<button class="btn btn-secondary" type="button">Secondary</button>
<button class="btn btn-success" type="button">Success</button>
<button class="btn btn-info" type="button">Info</button>
<button class="btn btn-warning" type="button">Warning</button>
<button class="btn btn-danger" type="button">Danger</button>
<button class="btn btn-light" type="button">Light</button>
<button class="btn btn-dark" type="button">Dark</button>
<button class="btn btn-auto" type="button">Auto</button>

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.

<a class="btn btn-primary" href="#" role="button">Link</a>
<button class="btn btn-primary" type="submit">Button</button>
<input class="btn btn-primary" type="button" value="Input">
<input class="btn btn-primary" type="submit" value="Submit">
<input class="btn btn-primary" type="reset" value="Reset">

Sizes

Fancy larger or smaller buttons? Add .btn-lg or .btn-sm for additional sizes.

<button class="btn btn-lg btn-primary" type="button">Large button</button>

<button class="btn btn-sm btn-primary" type="button">Small button</button>

Create block level buttons - those that span the full width of a parent - by adding .w-100.

<button class="btn btn-lg btn-primary w-100" type="button">Block level button</button>

Disabled state

Make buttons look inactive by adding the disabled boolean attribute to any <button> element. Disabled buttons have pointer-events: none; applied to, preventing hover and active states from triggering.

<button class="btn btn-primary" type="button" disabled>Disabled button</button>

Disabled buttons using the <a> element behave a bit different:

• <a>s don’t support the disabled 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.

<a class="btn btn-primary disabled" href="#" tabindex="-1" role="button" aria-disabled="true">Disabled link</a>

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.

Button plugin

The button plugin allows you to create simple on/off toggle buttons.

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>.

<button class="btn btn-primary" data-toggle="button" autocomplete="off" type="button">Toggle button</button>
<button class="btn btn-primary active" data-toggle="button" autocomplete="off" type="button" aria-pressed="true">Active toggle button</button>
<button class="btn btn-primary" data-toggle="button" autocomplete="off" type="button" disabled>Disabled toggle button</button>

<a class="btn btn-primary mr-3 mb-3" data-toggle="button" href="#" role="button">Toggle link</a>
<a class="btn btn-primary active mr-3 mb-3" data-toggle="button" href="#" role="button" aria-pressed="true">Active toggle link</a>
<a class="btn btn-primary disabled mb-3" data-toggle="button" href="#" role="button">Disabled toggle link</a>