From 1ded0d6a4eefb7daca62c44e4e735aec200f0b6f Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Mon, 11 Feb 2019 11:15:34 -0800 Subject: Release v4.3.0 (#28228) * Prep for v4.3.0 * More updates for v4.3.0. * rerun to build docs source map --- site/docs/4.3/components/button-group.md | 207 +++++++++++++++++++++++++++++++ 1 file changed, 207 insertions(+) create mode 100644 site/docs/4.3/components/button-group.md (limited to 'site/docs/4.3/components/button-group.md') diff --git a/site/docs/4.3/components/button-group.md b/site/docs/4.3/components/button-group.md new file mode 100644 index 000000000..2261a5e72 --- /dev/null +++ b/site/docs/4.3/components/button-group.md @@ -0,0 +1,207 @@ +--- +layout: docs +title: Button group +description: Group a series of buttons together on a single line with the button group, and super-power them with JavaScript. +group: components +toc: true +--- + +## Basic example + +Wrap a series of buttons with `.btn` in `.btn-group`. Add on optional JavaScript radio and checkbox style behavior with [our buttons plugin]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/buttons/#button-plugin). + +{% capture example %} +
+ + + +
+{% endcapture %} +{% include example.html content=example %} + +{% capture callout %} +##### Ensure correct `role` and provide a label + +In order for assistive technologies (such as screen readers) to convey that a series of buttons is grouped, an appropriate `role` attribute needs to be provided. For button groups, this would be `role="group"`, while toolbars should have a `role="toolbar"`. + +In addition, groups and toolbars should be given an explicit label, as most assistive technologies will otherwise not announce them, despite the presence of the correct role attribute. In the examples provided here, we use `aria-label`, but alternatives such as `aria-labelledby` can also be used. +{% endcapture %} +{% include callout.html content=callout type="warning" %} + +## Button toolbar + +Combine sets of button groups into button toolbars for more complex components. Use utility classes as needed to space out groups, buttons, and more. + +{% capture example %} + +{% endcapture %} +{% include example.html content=example %} + +Feel free to mix input groups with button groups in your toolbars. Similar to the example above, you'll likely need some utilities though to space things properly. + +{% capture example %} + + + +{% endcapture %} +{% include example.html content=example %} + +## Sizing + +Instead of applying button sizing classes to every button in a group, just add `.btn-group-*` to each `.btn-group`, including each one when nesting multiple groups. + +
+
+ + + +
+
+
+ + + +
+
+
+ + + +
+
+ +{% highlight html %} +
...
+
...
+
...
+{% endhighlight %} + +## Nesting + +Place a `.btn-group` within another `.btn-group` when you want dropdown menus mixed with a series of buttons. + +{% capture example %} +
+ + + +
+ +
+ Dropdown link + Dropdown link +
+
+
+{% endcapture %} +{% include example.html content=example %} + +## Vertical variation + +Make a set of buttons appear vertically stacked rather than horizontally. **Split button dropdowns are not supported here.** + +
+
+ + + + + + +
+
+ + +
+
+ + +
+ +
+ Dropdown link + Dropdown link +
+
+ + +
+ +
+ Dropdown link + Dropdown link +
+
+
+ +
+ Dropdown link + Dropdown link +
+
+
+ +
+ Dropdown link + Dropdown link +
+
+
+
+ +{% highlight html %} +
+ ... +
+{% endhighlight %} -- cgit v1.2.3