<pclass="lead">Provide pagination links for your site or app with the multi-page pagination component, or the simpler <ahref="./components.html#pagination-pager">pager alternative</a>.</p>
<pclass="lead">Provide pagination links for your site or app with the multi-page pagination component, or the simpler <ahref="./components.html#pagination-pager">pager alternative</a>.</p>
<p>Simple pagination inspired by Rdio, great for apps and search results. The large block is hard to miss, easily scalable, and provides large click areas.</p>
<p>Simple pagination inspired by Rdio, great for apps and search results. The large block is hard to miss, easily scalable, and provides large click areas.</p>
<divclass="bs-docs-example">
<divclass="bs-docs-example">
<ulclass="pagination">
<ulclass="pagination">
...
@@ -3778,15 +3774,13 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -3778,15 +3774,13 @@ For example, <code><section></code> should be wrapped as inline.
<p>A simple shell for an <code>h1</code> to appropriately space out and segment sections of content on a page. It can utilize the <code>h1</code>'s default <code>small</code>, element as well most other components (with additional styles).</p>
<p>A simple shell for an <code>h1</code> to appropriately space out and segment sections of content on a page. It can utilize the <code>h1</code>'s default <code>small</code>, element as well most other components (with additional styles).</p>
<divclass="bs-docs-example">
<divclass="bs-docs-example">
<divclass="page-header">
<divclass="page-header">
...
@@ -3957,14 +3950,13 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -3957,14 +3950,13 @@ For example, <code><section></code> should be wrapped as inline.
<h1>Example page header <small>Subtext for header</small></h1>
<h1>Example page header <small>Subtext for header</small></h1>
<pclass="lead">Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages. For inline dismissal, use the <ahref="./javascript.html#alerts">alerts jQuery plugin</a>.</p>
<pclass="lead">Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages. For inline dismissal, use the <ahref="./javascript.html#alerts">alerts jQuery plugin</a>.</p>
<h3>Default alert</h3>
<h3id="alerts-default">Default alert</h3>
<p>Wrap any text and an optional dismiss button in <code>.alert</code> for a basic warning alert message. <strong>To ensure proper behavior across all devices</strong>, be sure to use <code><button></code> element with the <code>data-dismiss="alert"</code> data attribute.</p>
<p>Wrap any text and an optional dismiss button in <code>.alert</code> for a basic warning alert message. <strong>To ensure proper behavior across all devices</strong>, be sure to use <code><button></code> element with the <code>data-dismiss="alert"</code> data attribute.</p>
<divclass="bs-docs-example">
<divclass="bs-docs-example">
<divclass="alert">
<divclass="alert">
...
@@ -4087,7 +4077,7 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -4087,7 +4077,7 @@ For example, <code><section></code> should be wrapped as inline.
</div>
</div>
{% endhighlight %}
{% endhighlight %}
<h3>Block alerts</h3>
<h3id="alerts-block">Block alerts</h3>
<p>For longer messages, increase the padding on the top and bottom of the alert wrapper by adding <code>.alert-block</code>.</p>
<p>For longer messages, increase the padding on the top and bottom of the alert wrapper by adding <code>.alert-block</code>.</p>
<divclass="bs-docs-example">
<divclass="bs-docs-example">
<divclass="alert alert-block">
<divclass="alert alert-block">
...
@@ -4104,7 +4094,7 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -4104,7 +4094,7 @@ For example, <code><section></code> should be wrapped as inline.
@@ -4140,7 +4130,7 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -4140,7 +4130,7 @@ For example, <code><section></code> should be wrapped as inline.
<p>Progress bars use CSS3 transitions and animations to achieve some of their effects. These features are not supported in IE8-9 or older versions of Firefox. Internet Explorer 10 and below, as well as Opera 12, do not support animations.</p>
<p>Progress bars use CSS3 transitions and animations to achieve some of their effects. These features are not supported in IE8-9 or older versions of Firefox. Internet Explorer 10 and below, as well as Opera 12, do not support animations.</p>
<h3>Basic</h3>
<h3id="progress-basic">Basic</h3>
<p>Default progress bar with a vertical gradient.</p>
<p>Default progress bar with a vertical gradient.</p>
<divclass="bs-docs-example">
<divclass="bs-docs-example">
<divclass="progress">
<divclass="progress">
...
@@ -4153,7 +4143,7 @@ For example, <code><section></code> should be wrapped as inline.
...
@@ -4153,7 +4143,7 @@ For example, <code><section></code> should be wrapped as inline.
<h3id="js-individual-compiled">Individual or compiled</h3>
<p>Plugins can be included individually (though some have required dependencies), or all at once. <strong>Do attempt to include both.</strong> Both <strong>bootstrap.js</strong> and <strong>bootstrap.min.js</strong> contain all plugins in a single file.</p>
<p>Plugins can be included individually (though some have required dependencies), or all at once. <strong>Do attempt to include both.</strong> Both <strong>bootstrap.js</strong> and <strong>bootstrap.min.js</strong> contain all plugins in a single file.</p>
<h3>Data attributes</h3>
<h3id="js-data-attrs">Data attributes</h3>
<p>You can use all Bootstrap plugins purely through the markup API without writing a single line of JavaScript. This is Bootstrap's first class API and should be your first consideration when using a plugin.</p>
<p>You can use all Bootstrap plugins purely through the markup API without writing a single line of JavaScript. This is Bootstrap's first class API and should be your first consideration when using a plugin.</p>
<p>That said, in some situations it may be desirable to turn this functionality off. Therefore, we also provide the ability to disable the data attribute API by unbinding all events on the body namespaced with `'data-api'`. This looks like this:
<p>That said, in some situations it may be desirable to turn this functionality off. Therefore, we also provide the ability to disable the data attribute API by unbinding all events on the body namespaced with `'data-api'`. This looks like this:
...
@@ -4447,7 +4434,7 @@ $('body').off('.data-api')
...
@@ -4447,7 +4434,7 @@ $('body').off('.data-api')
$('body').off('.alert.data-api')
$('body').off('.alert.data-api')
{% endhighlight %}
{% endhighlight %}
<h3>Programmatic API</h3>
<h3id="js-programmatic-api">Programmatic API</h3>
<p>We also believe you should be able to use all Bootstrap plugins purely through the JavaScript API. All public APIs are single, chainable methods, and return the collection acted upon.</p>
<p>We also believe you should be able to use all Bootstrap plugins purely through the JavaScript API. All public APIs are single, chainable methods, and return the collection acted upon.</p>
{% highlight js linenos %}
{% highlight js linenos %}
$(".btn.danger").button("toggle").addClass("fat")
$(".btn.danger").button("toggle").addClass("fat")
...
@@ -4462,15 +4449,14 @@ $("#myModal").modal('show') // initializes and invokes show immed
...
@@ -4462,15 +4449,14 @@ $("#myModal").modal('show') // initializes and invokes show immed
<p>Each plugin also exposes its raw constructor on a `Constructor` property: <code>$.fn.popover.Constructor</code>. If you'd like to get a particular plugin instance, retrieve it directly from an element: <code>$('[rel=popover]').data('popover')</code>.</p>
<p>Each plugin also exposes its raw constructor on a `Constructor` property: <code>$.fn.popover.Constructor</code>. If you'd like to get a particular plugin instance, retrieve it directly from an element: <code>$('[rel=popover]').data('popover')</code>.</p>
<h3>No conflict</h3>
<h3id="js-noconflict">No conflict</h3>
<p>Sometimes it is necessary to use Bootstrap plugins with other UI frameworks. In these circumstances, namespace collisions can occasionally occur. If this happens, you may call <code>.noConflict</code> on the plugin you wish to revert the value of.</p>
<p>Sometimes it is necessary to use Bootstrap plugins with other UI frameworks. In these circumstances, namespace collisions can occasionally occur. If this happens, you may call <code>.noConflict</code> on the plugin you wish to revert the value of.</p>
{% highlight js linenos %}
{% highlight js linenos %}
var bootstrapButton = $.fn.button.noConflict() // return $.fn.button to previously assigned value
var bootstrapButton = $.fn.button.noConflict() // return $.fn.button to previously assigned value
$.fn.bootstrapBtn = bootstrapButton // give $().bootstrapBtn the bootstrap functionality
$.fn.bootstrapBtn = bootstrapButton // give $().bootstrapBtn the bootstrap functionality
{% endhighlight %}
{% endhighlight %}
<h3id="js-events">Events</h3>
<h3>Events</h3>
<p>Bootstrap provides custom events for most plugin's unique actions. Generally, these come in an infinitive and past participle form - where the infinitive (ex. <code>show</code>) is triggered at the start of an event, and its past participle form (ex. <code>shown</code>) is trigger on the completion of an action.</p>
<p>Bootstrap provides custom events for most plugin's unique actions. Generally, these come in an infinitive and past participle form - where the infinitive (ex. <code>show</code>) is triggered at the start of an event, and its past participle form (ex. <code>shown</code>) is trigger on the completion of an action.</p>
<p>All infinitive events provide <code>preventDefault</code> functionality. This provides the ability to stop the execution of an action before it starts.</p>
<p>All infinitive events provide <code>preventDefault</code> functionality. This provides the ability to stop the execution of an action before it starts.</p>
{% highlight js linenos %}
{% highlight js linenos %}
...
@@ -4478,14 +4464,13 @@ $('#myModal').on('show', function (e) {
...
@@ -4478,14 +4464,13 @@ $('#myModal').on('show', function (e) {
if (!data) return e.preventDefault() // stops modal from being shown
if (!data) return e.preventDefault() // stops modal from being shown
<p>Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.</p>
<p>Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.</p>
<h3>Static example</h3>
<h3>Static example</h3>
...
@@ -4626,7 +4610,7 @@ $('#myModal').on('show', function (e) {
...
@@ -4626,7 +4610,7 @@ $('#myModal').on('show', function (e) {
<h2>Usage</h2>
<h2id="modals-usage">Usage</h2>
<h3>Via data attributes</h3>
<h3>Via data attributes</h3>
<p>Activate a modal without writing JavaScript. Set <code>data-toggle="modal"</code> on a controller element, like a button, along with a <code>data-target="#foo"</code> or <code>href="#foo"</code> to target a specific modal to toggle.</p>
<p>Activate a modal without writing JavaScript. Set <code>data-toggle="modal"</code> on a controller element, like a button, along with a <code>data-target="#foo"</code> or <code>href="#foo"</code> to target a specific modal to toggle.</p>
...
@@ -4735,7 +4719,7 @@ $('#myModal').on('hidden', function () {
...
@@ -4735,7 +4719,7 @@ $('#myModal').on('hidden', function () {