From 0ded703f6bb7b0c60b1ec8e90592c845ca07d46e Mon Sep 17 00:00:00 2001 From: andyexeter Date: Thu, 15 Sep 2016 10:33:11 +0100 Subject: Implement container option for tooltips and popovers. --- docs/components/tooltips.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/components') diff --git a/docs/components/tooltips.md b/docs/components/tooltips.md index b6dc451ec..31fb2c1c7 100644 --- a/docs/components/tooltips.md +++ b/docs/components/tooltips.md @@ -165,7 +165,7 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap container - string | false + string | element | false false

Appends the tooltip to a specific element. Example: container: 'body'. This option is particularly useful in that it allows you to position the tooltip in the flow of the document near the triggering element - which will prevent the tooltip from floating away from the triggering element during a window resize.

-- cgit v1.2.3 From 25216349b38d1cff78ae5b2febc0fe252e983f0f Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Sat, 26 Nov 2016 00:19:30 -0800 Subject: add some disabled navbar link examples --- docs/components/navbar.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/components') diff --git a/docs/components/navbar.md b/docs/components/navbar.md index 34fb6f28b..06a90a212 100644 --- a/docs/components/navbar.md +++ b/docs/components/navbar.md @@ -44,7 +44,7 @@ Here's an example of all the sub-components included in a default, non-responsiv Link @@ -132,7 +132,7 @@ And because we use classes for our navs, you can avoid the list-based approach e Home (current) Features Pricing - About + Disabled {% endexample %} -- cgit v1.2.3 From e17e75b7574d6877facb0eadd977c025a09fd749 Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Sat, 26 Nov 2016 16:55:18 -0800 Subject: Update inline forms (updated docs and new flexbox styles) (#21212) * fix form-inline with flex enabled * grunt * fix alignment of labels * shorter if syntax * add new form example to docs for now * update inline form docs usage guidelines * responsive margins * better margin utils * fix sizing of .form-check * flexbox alignment of .form-check * no need to change direction * support custom controls in inline form, for default and flex modes * add example of custom select and checks to docs * remove hidden and visible label variants since we cover that in the usage guidelines at the start and include hidden labels everywhere * use property value instead of layout name * apply to all labels * add a visible label, space it out * add id --- docs/components/forms.md | 72 +++++++++++++++++++++--------------------------- 1 file changed, 32 insertions(+), 40 deletions(-) (limited to 'docs/components') diff --git a/docs/components/forms.md b/docs/components/forms.md index 8915c9e7b..dd3e0027f 100644 --- a/docs/components/forms.md +++ b/docs/components/forms.md @@ -274,62 +274,54 @@ The `.form-group` class is the easiest way to add some structure to forms. Its o ### Inline forms -Use the `.form-inline` class to display a series of labels, form controls, and buttons on a single horizontal row. Form controls within inline forms behave differently: +Use the `.form-inline` class to display a series of labels, form controls, and buttons on a single horizontal row. Form controls within inline forms vary slightly from their default states. -- Controls are `display: inline-block` to provide alignment control via `vertical-align` and `margin`. -- Controls receive `width: auto` to override the Bootstrap default `width: 100%`. -- Controls **only appear inline in viewports that are at least 768px wide** to account for narrow viewports on mobile devices. +- Controls are `display: inline-block` (or `flex` when enabled) to provide alignment control via `vertical-align` and `margin`. Those also means you'll have some HTML character spaces between elements by default. +- Controls and input groups receive `width: auto` to override the Bootstrap default `width: 100%`. +- Controls **only appear inline in viewports that are at least 576px wide** to account for narrow viewports on mobile devices. -Because of this, you may need to manually address the width and alignment of individual form controls. Lastly, as shown below, you should always include a `