From: Mark Otto Date: Sun, 14 Apr 2013 05:10:34 +0000 (-0700) Subject: swap all bold p tags in sidenotes for h4s X-Git-Tag: v3.0.0-rc1~442 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc8b9fb07df5d63a162c94ba165bc3759ec2a889;p=thirdparty%2Fbootstrap.git swap all bold p tags in sidenotes for h4s --- diff --git a/docs/assets/css/docs.css b/docs/assets/css/docs.css index b6117e9279..2ec7799edf 100644 --- a/docs/assets/css/docs.css +++ b/docs/assets/css/docs.css @@ -39,6 +39,9 @@ body { background-color: #fcf2f2; border-left: 5px solid #df7c7b; } +.bs-docs-sidenote h4 { + margin-top: 0; +} .bs-docs-sidenote p:last-child { margin-bottom: 0; } @@ -662,6 +665,7 @@ input.focused { margin-bottom: 0; background-color: transparent; border: 0; + white-space: nowrap; } .highlight pre code { font-size: inherit; diff --git a/docs/docs.html b/docs/docs.html index 6d6888e040..258dabe1da 100644 --- a/docs/docs.html +++ b/docs/docs.html @@ -207,7 +207,7 @@ title: Bootstrap Documentation

Once you've downloaded and included Bootstrap's CSS into your templates, you can move on to customizing the included components. To do so, create a new stylesheet (LESS, if you like, or just plain CSS) to house your customizations.

-

Compiled or minified?

+

Compiled or minified?

Unless you plan on reading a good chunk of the compiled CSS, go with the minified. It's the same code, just compacted. Less bandwidth is good, especially in production environments.

@@ -261,7 +261,7 @@ title: Bootstrap Documentation

Going beyond light customizations and into visual overhauls is just as straightforward as the above custom button. For a site like Karma, which uses Bootstrap as a CSS reset with heavy modifications, more extensive work is involved, but well worth it in the end.

-

Alternate customization methods

+

Alternate customization methods

While not recommended for folks new to Bootstrap, you may use one of two alternate methods for customization. The first is modifying the source .less files (making upgrades super difficult), and the second is mapping source LESS code to your own classes via mixins. For the time being, neither options are documented here.

@@ -2104,7 +2104,7 @@ For example, <section> should be wrapped as inline. {% endhighlight %}
-

Cross-browser compatibility

+

Cross-browser compatibility

If you add the disabled attribute to a <button>, Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cannot fix.

@@ -2562,7 +2562,7 @@ For example, <section> should be wrapped as inline. {% endhighlight %}
-

Accessibility

+

Accessibility

Keep in mind that using icons without any additional content means the icons are not represented to screen reader users.

@@ -3603,7 +3603,7 @@ For example, <section> should be wrapped as inline. {% endhighlight %}
-

Plugin dependency

+

Plugin dependency

The responsive navbar requires the collapse plugin to be included in your version of Bootstrap.

@@ -4187,7 +4187,7 @@ For example, <section> should be wrapped as inline.

Provide up-to-date feedback on the progress of a workflow or action with simple yet flexible progress bars.

-

Cross-browser compatibility

+

Cross-browser compatibility

Progress bars use CSS3 transitions and animations to achieve some of their effects.

These features are not supported in Internet Explorer 9 and below or older versions of Firefox. Opera 12 does not support animations.

@@ -5290,7 +5290,7 @@ $('.navbar').scrollspy() {% endhighlight %}
-

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

@@ -5579,7 +5579,7 @@ $('#example').tooltip(options)
-

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.

@@ -5759,7 +5759,7 @@ $('#example').tooltip(options)
-

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.

@@ -5979,7 +5979,7 @@ $('.nav-tabs').button()

$().button('toggle')

Toggles push state. Gives the button the appearance that it has been activated.

-

Auto toggling

+

Auto toggling

You can enable auto toggling of a button by using the data-toggle attribute.

{% highlight html linenos %} @@ -5994,7 +5994,7 @@ $('.nav-tabs').button() {% endhighlight %}
-

Cross-browser compatibility

+

Cross-browser compatibility

Firefox persists the disabled state across page loads. A workaround for this is to use autocomplete="off".

@@ -6547,7 +6547,7 @@ $('.typeahead').typeahead() {% endhighlight %}
-

Heads up!

+

Requires positioning

You must manage the position of a pinned element and the behavior of its immediate parent. Position is controlled by affix, affix-top, and affix-bottom. Remember to check for a potentially collapsed parent when the affix kicks in as it's removing content from the normal flow of the page.