Buttons

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

Examples

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

<button type="button" class="btn_sth btn-primary_sth">Primary</button>
<button type="button" class="btn_sth btn-secondary_sth">Secondary</button>
<button type="button" class="btn_sth btn-success_sth">Success</button>
<button type="button" class="btn_sth btn-danger_sth">Danger</button>
<button type="button" class="btn_sth btn-warning_sth">Warning</button>
<button type="button" class="btn_sth btn-info_sth">Info</button>
<button type="button" class="btn_sth btn-light_sth">Light</button>
<button type="button" class="btn_sth btn-dark_sth">Dark</button>

<button type="button" class="btn_sth btn-link_sth">Link</button>

Conveying meaning to assistive technologies

Using color to add meaning only provides a visual indication, which will not be conveyed to users of assistive technologies – such as screen readers. Ensure that information denoted by the color is either obvious from the content itself (e.g. the visible text), or is included through alternative means, such as additional text hidden with the .sr-only class.

Button tags

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

Link

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

Outline buttons

In need of a button, but not the hefty background colors they bring? Replace the default modifier classes with the .btn-outline-*_sth ones to remove all background images and colors on any button.

<button type="button" class="btn_sth btn-outline-primary_sth">Primary</button>
<button type="button" class="btn_sth btn-outline-secondary_sth">Secondary</button>
<button type="button" class="btn_sth btn-outline-success_sth">Success</button>
<button type="button" class="btn_sth btn-outline-danger_sth">Danger</button>
<button type="button" class="btn_sth btn-outline-warning_sth">Warning</button>
<button type="button" class="btn_sth btn-outline-info_sth">Info</button>
<button type="button" class="btn_sth btn-outline-light_sth">Light</button>
<button type="button" class="btn_sth btn-outline-dark_sth">Dark</button>

Sizes

Fancy larger or smaller buttons? Add .btn-lg_sth or .btn-sm_sth for additional sizes.

<button type="button" class="btn_sth btn-primary_sth btn-lg_sth">Large button</button>
<button type="button" class="btn_sth btn-secondary_sth btn-lg_sth">Large button</button>

<button type="button" class="btn_sth btn-primary_sth btn-sm_sth">Small button</button>
<button type="button" class="btn_sth btn-secondary_sth btn-sm_sth">Small button</button>

Create block level buttons—those that span the full width of a parent—by adding .btn-block_sth.

<button type="button" class="btn_sth btn-primary_sth btn-lg_sth btn-block_sth">Block level button</button>
<button type="button" class="btn_sth btn-secondary_sth btn-lg_sth btn-block_sth">Block level button</button>

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_sth (and include the aria-pressed="true" attribute) should you need to replicate the state programmatically.

Primary link Link

<a href="#" class="btn_sth btn-primary_sth btn-lg active_sth" role="button" aria-pressed="true">Primary link</a>
<a href="#" class="btn_sth btn-secondary_sth btn-lg_sth active_sth" role="button" aria-pressed="true">Link</a>

Disabled state

Make buttons look inactive by adding the disabled boolean attribute to any <button> element.

<button type="button" class="btn_sth btn-lg_sth btn-primary_sth" disabled>Primary button</button>
<button type="button" class="btn_sth btn-secondary_sth btn-lg_sth" 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.

Primary link Link

<a href="#" class="btn_sth btn-primary_sth btn-lg_sth disabled_sth" role="button" aria-disabled="true">Primary link</a>
<a href="#" class="btn_sth btn-secondary_sth btn-lg_sth disabled_sth" role="button" aria-disabled="true">Link</a>

Link functionality caveat

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

Do more with buttons. Control button states or create groups of buttons for more components like toolbars.

Toggle states

Add data-toggle_sth="button" to toggle a button’s active state. If you’re pre-toggling a button, you must manually add the .active_sth class and aria-pressed="true" to the <button>.

<button type="button" class="btn_sth btn-primary_sth" data-toggle_sth="button" aria-pressed="false" autocomplete="off">
  Single toggle
</button>

Checkbox and radio buttons

InPage’s .button_sth styles can be applied to other elements, such as <label>s, to provide checkbox or radio style button toggling. Add data-toggle_sth="buttons" to a .btn-group_sth 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_sth on the <label> manually.

Note that pre-checked buttons require you to manually add the .active_sth class to the input’s <label>.

Checkbox 1 (pre-checked) Checkbox 2 Checkbox 3

<div class="btn-group_sth" data-toggle_sth="buttons">
  <label class="btn_sth btn-secondary_sth active_sth">
    <input type="checkbox" checked autocomplete="off"> Checkbox 1 (pre-checked)
  </label>
  <label class="btn_sth btn-secondary_sth">
    <input type="checkbox" autocomplete="off"> Checkbox 2
  </label>
  <label class="btn_sth btn-secondary_sth">
    <input type="checkbox" autocomplete="off"> Checkbox 3
  </label>
</div>

Radio 1 (preselected) Radio 2 Radio 3

<div class="btn-group_sth" data-toggle_sth="buttons">
  <label class="btn_sth btn-secondary_sth active_sth">
    <input type="radio" name="options" id="option1" autocomplete="off" checked> Radio 1 (preselected)
  </label>
  <label class="btn_sth btn-secondary_sth">
    <input type="radio" name="options" id="option2" autocomplete="off"> Radio 2
  </label>
  <label class="btn_sth btn-secondary_sth">
    <input type="radio" name="options" id="option3" autocomplete="off"> Radio 3
  </label>
</div>

Methods

Method	Description
`$sth().button('toggle')`	Toggles push state. Gives the button the appearance that it has been activated.
`$sth().button('dispose')`	Destroys an element’s button.