2
0
mirror of https://github.com/tenrok/bootstrap.git synced 2026-06-11 18:02:28 +03:00

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.
This commit is contained in:
XhmikosR
2018-11-11 12:07:42 +02:00
parent cb2b21bb88
commit 11da160114
7 changed files with 9 additions and 9 deletions
+1 -1
View File
@@ -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 %}
+2 -2
View File
@@ -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 %}
+2 -2
View File
@@ -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 %}
+1 -1
View File
@@ -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 %}