diff options
author | XhmikosR <xhmikosr@gmail.com> | 2018-11-11 13:07:42 +0300 |
---|---|---|
committer | XhmikosR <xhmikosr@gmail.com> | 2018-11-27 17:01:07 +0300 |
commit | 11da1601140174e4fa4e0e25e7f66fc21c08e927 (patch) | |
tree | 1af440d9def0d5a50c6d4d12820bfbc195449c78 | |
parent | cb2b21bb88604dee22bd4d0f2804d8366b2d65e3 (diff) |
Use `h5` for callouts so that they are not included in ToC.
Callouts are already excluded from ToC, but due to a limitation in jekyll-toc they are still being included.
We should revisit this if the bug is fixed later.
-rw-r--r-- | site/_includes/callout-danger-async-methods.md | 2 | ||||
-rw-r--r-- | site/docs/4.1/components/forms.md | 2 | ||||
-rw-r--r-- | site/docs/4.1/components/popovers.md | 4 | ||||
-rw-r--r-- | site/docs/4.1/components/scrollspy.md | 4 | ||||
-rw-r--r-- | site/docs/4.1/components/tooltips.md | 2 | ||||
-rw-r--r-- | site/docs/4.1/getting-started/javascript.md | 2 | ||||
-rw-r--r-- | site/docs/4.1/utilities/colors.md | 2 |
7 files changed, 9 insertions, 9 deletions
diff --git a/site/_includes/callout-danger-async-methods.md b/site/_includes/callout-danger-async-methods.md index 083f28f238..951ba76ccf 100644 --- a/site/_includes/callout-danger-async-methods.md +++ b/site/_includes/callout-danger-async-methods.md @@ -1,5 +1,5 @@ {% capture callout %} -#### Asynchronous methods and transitions +##### Asynchronous methods and transitions All API methods are **asynchronous** and start a **transition**. They return to the caller as soon as the transition is started but **before it ends**. In addition, a method call on a **transitioning component will be ignored**. diff --git a/site/docs/4.1/components/forms.md b/site/docs/4.1/components/forms.md index 29f7fc10bc..1ea3e1a4d3 100644 --- a/site/docs/4.1/components/forms.md +++ b/site/docs/4.1/components/forms.md @@ -737,7 +737,7 @@ By default, browsers will treat all native form controls (`<input>`, `<select>` {% include callout.html content=callout type="warning" %} {% capture callout %} -#### Cross-browser compatibility +##### Cross-browser compatibility While Bootstrap will apply these styles in all browsers, Internet Explorer 11 and below don't fully support the `disabled` attribute on a `<fieldset>`. Use custom JavaScript to disable the fieldset in these browsers. {% endcapture %} diff --git a/site/docs/4.1/components/popovers.md b/site/docs/4.1/components/popovers.md index f55826d7ca..d26cb278a6 100644 --- a/site/docs/4.1/components/popovers.md +++ b/site/docs/4.1/components/popovers.md @@ -99,7 +99,7 @@ sagittis lacus vel augue laoreet rutrum faucibus."> Use the `focus` trigger to dismiss popovers on the user's next click of a different element than the toggle element. {% capture callout %} -#### Specific markup required for dismiss-on-next-click +##### Specific markup required for dismiss-on-next-click For proper cross-browser and cross-platform behavior, you must use the `<a>` tag, _not_ the `<button>` tag, and you also must include a [`tabindex`](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex) attribute. {% endcapture %} @@ -253,7 +253,7 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap </table> {% capture callout %} -#### Data attributes for individual popovers +##### Data attributes for individual popovers Options for individual popovers can alternatively be specified through the use of data attributes, as explained above. {% endcapture %} diff --git a/site/docs/4.1/components/scrollspy.md b/site/docs/4.1/components/scrollspy.md index 3c52f82510..015e0ca42d 100644 --- a/site/docs/4.1/components/scrollspy.md +++ b/site/docs/4.1/components/scrollspy.md @@ -257,14 +257,14 @@ $('body').scrollspy({ target: '#navbar-example' }) {% endhighlight %} {% capture callout %} -#### Resolvable ID targets required +##### Resolvable ID targets required Navbar links must have resolvable id targets. For example, a `<a href="#home">home</a>` must correspond to something in the DOM like `<div id="home"></div>`. {% endcapture %} {% include callout.html content=callout type="danger" %} {% capture callout %} -#### Non-`:visible` target elements ignored +##### Non-`:visible` target elements ignored Target elements that are not [`:visible` according to jQuery](https://api.jquery.com/visible-selector/) will be ignored and their corresponding nav items will never be highlighted. {% endcapture %} diff --git a/site/docs/4.1/components/tooltips.md b/site/docs/4.1/components/tooltips.md index aa3ebe077c..fffa795fd1 100644 --- a/site/docs/4.1/components/tooltips.md +++ b/site/docs/4.1/components/tooltips.md @@ -254,7 +254,7 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap </table> {% capture callout %} -#### Data attributes for individual tooltips +##### Data attributes for individual tooltips Options for individual tooltips can alternatively be specified through the use of data attributes, as explained above. {% endcapture %} diff --git a/site/docs/4.1/getting-started/javascript.md b/site/docs/4.1/getting-started/javascript.md index 7f59ac213a..534e2fd420 100644 --- a/site/docs/4.1/getting-started/javascript.md +++ b/site/docs/4.1/getting-started/javascript.md @@ -35,7 +35,7 @@ $(document).off('.alert.data-api') {% endhighlight %} {% capture callout %} -## Selectors +##### Selectors Currently to query DOM elements we use the native methods `querySelector` and `querySelectorAll` for performance reasons, so you have to use [valid selectors](https://www.w3.org/TR/CSS21/syndata.html#value-def-identifier). If you use special selectors, for example: `collapse:Example` be sure to escape them. diff --git a/site/docs/4.1/utilities/colors.md b/site/docs/4.1/utilities/colors.md index 55699adb8c..a1b1a9816f 100644 --- a/site/docs/4.1/utilities/colors.md +++ b/site/docs/4.1/utilities/colors.md @@ -49,7 +49,7 @@ When `$enable-gradients` is set to `true` (default is `false`), you can use `.bg - `.bg-gradient-{{ color.name }}`{% endfor %} {% capture callout %} -#### Dealing with specificity +##### Dealing with specificity Sometimes contextual classes cannot be applied due to the specificity of another selector. In some cases, a sufficient workaround is to wrap your element's content in a `<div>` with the class. {% endcapture %} |