diff --git a/docs/components.html b/docs/components.html index 4caa9e6f28..a400d216dc 100644 --- a/docs/components.html +++ b/docs/components.html @@ -185,7 +185,7 @@ lead: "Over a dozen reusable components built to provide iconography, dropdowns,

Group a series of buttons together on a single line with the button group. Add on optional JavaScript radio and checkbox style behavior with our buttons plugin.

-
+

Tooltips & popovers in button groups require special setting

When using tooltips or popovers on elements within a .btn-group, you'll have to specify the option container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).

@@ -755,11 +755,11 @@ lead: "Over a dozen reusable components built to provide iconography, dropdowns,

Cross-browser compatibility

Avoid using <select> elements here as they cannot be fully styled in WebKit browsers.

-
+

Tooltips & popovers in input groups require special setting

When using tooltips or popovers on elements within an .input-group, you'll have to specify the option container: 'body' to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip or popover is triggered).

-
+

Don't mix with other components

Do not mix form group or grid column classes directly with input groups.

@@ -1432,7 +1432,7 @@ lead: "Over a dozen reusable components built to provide iconography, dropdowns,

There are some caveats regarding using form controls within fixed elements on mobile devices. See our browser support docs for details.

-
+

Always add labels

Screen readers will have trouble with your forms if you don't include a label for every input. For these inline navbar forms, you can hide the labels using the .sr-only class.

diff --git a/docs/css.html b/docs/css.html index d8d6b8bb5b..643d1dc0eb 100644 --- a/docs/css.html +++ b/docs/css.html @@ -1588,7 +1588,7 @@ For example, <section> should be wrapped as inline.

Requires custom widths

Inputs, selects, and textareas are 100% wide by default in Bootstrap. To use the inline form, you'll have to set a width on the form controls used within.

-
+

Always add labels

Screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the .sr-only class.

@@ -2369,7 +2369,7 @@ For example, <section> should be wrapped as inline. ... {% endhighlight %} -
+

Responsive images

Looking for how to make images more responsive? Check out the responsive images section up top.

diff --git a/docs/javascript.html b/docs/javascript.html index d7035d6612..b568ff7a78 100644 --- a/docs/javascript.html +++ b/docs/javascript.html @@ -925,7 +925,7 @@ $('a[data-toggle="tab"]').on('shown.bs.tab', function (e) {

Opt-in functionality

For performance reasons, the Tooltip and Popover data-apis are opt-in, meaning you must initialize them yourself.

-
+

Tooltips in button groups and input groups require special setting

When using tooltips on elements within a .btn-group or an .input-group, you'll have to specify the option container: 'body' (documented below) to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the tooltip is triggered).

@@ -1110,7 +1110,7 @@ $('#myTooltip').on('hidden.bs.tooltip', function () {

Opt-in functionality

For performance reasons, the Tooltip and Popover data-apis are opt-in, meaning you must initialize them yourself.

-
+

Popovers in button groups and input groups require special setting

When using popovers on elements within a .btn-group or an .input-group, you'll have to specify the option container: 'body' (documented below) to avoid unwanted side effects (such as the element growing wider and/or losing its rounded corners when the popover is triggered).