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**.
@@ -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.
@@ -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.
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.
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.
@@ -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.