Design patterns that serve as basic building blocks.
Use kimsQ RC’s custom button styles for actions in forms, dialogs, and more. Includes support for a handful of contextual variations, sizes, states, and more.
kimsQ RC includes six predefined button styles, each serving its own semantic purpose.
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
.btn classes are designed to be used with the
<button> element. However, you can also use these classes on
<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.
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.
본 버튼은 Floating action buttons의 용도로 사용됩니다. 포지션 유틸리티와 같이 사용하면 좋습니다.
Fancy larger or smaller buttons? Add
.btn-sm for additional sizes.
Create block level buttons—those that span the full width of a parent—by adding
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.
Make buttons look inactive by adding the
disabled boolean attribute to any
Heads up! IE9 and below render disabled buttons with gray, shadowed text that we can’t override.
Disabled buttons using the
<a> element behave a bit different:
<a>s don’t support the
disabledattribute, so you must add the
.disabledclass to make it visually appear disabled.
pointer-eventson anchor buttons. In browsers which support that property, you won’t see the disabled cursor at all.
aria-disabled="true"attribute to indicate the state of the element to assistive technologies.
.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
Do more with buttons. Control button states or create groups of buttons for more components like toolbars.
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 type="button" class="btn btn-primary" data-toggle="button" aria-pressed="false" autocomplete="off"> Single toggle </button>
.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
Note that pre-checked buttons require you to manually add the
.active class to the input’s
<div class="btn-group" data-toggle="buttons"> <label class="btn btn-primary active"> <input type="checkbox" checked autocomplete="off"> Checkbox 1 (pre-checked) </label> <label class="btn btn-primary"> <input type="checkbox" autocomplete="off"> Checkbox 2 </label> <label class="btn btn-primary"> <input type="checkbox" autocomplete="off"> Checkbox 3 </label> </div>
<div class="btn-group" data-toggle="buttons"> <label class="btn btn-primary active"> <input type="radio" name="options" id="option1" autocomplete="off" checked> Radio 1 (preselected) </label> <label class="btn btn-primary"> <input type="radio" name="options" id="option2" autocomplete="off"> Radio 2 </label> <label class="btn btn-primary"> <input type="radio" name="options" id="option3" autocomplete="off"> Radio 3 </label> </div>
||Toggles push state. Gives the button the appearance that it has been activated.|