@@ -779,29 +779,25 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -779,29 +779,25 @@ For example, <code>section</code> should be wrapped as inline.
<divclass="page-header">
<divclass="page-header">
<h1>Forms</h1>
<h1>Forms</h1>
</div>
</div>
<divclass="row">
<divclass="span4">
<h2>Flexible HTML and CSS</h2>
<h2>Flexible HTML and CSS</h2>
<p>The best part about forms in Bootstrap is that all your inputs and controls look great no matter how you build them in your markup. No superfluous HTML is required, but we provide the patterns for those who require it.</p>
<p>The best part about forms in Bootstrap is that all your inputs and controls look great no matter how you build them in your markup. No superfluous HTML is required, but we provide the patterns for those who require it.</p>
<p>More complicated layouts come with succinct and scalable classes for easy styling and event binding, so you're covered at every step.</p>
<p>More complicated layouts come with succinct and scalable classes for easy styling and event binding, so you're covered at every step.</p>
</div>
<h2>Four layouts included</h2>
<divclass="span4">
<p>Bootstrap comes with support for four types of form layouts:</p>
<h2>Four layouts included</h2>
<ul>
<p>Bootstrap comes with support for four types of form layouts:</p>
<li>Vertical (default)</li>
<ul>
<li>Search</li>
<li>Vertical (default)</li>
<li>Inline</li>
<li>Search</li>
<li>Horizontal</li>
<li>Inline</li>
</ul>
<li>Horizontal</li>
<p>Different types of form layouts require some changes to markup, but the controls themselves remain and behave the same.</p>
</ul>
<p>Different types of form layouts require some changes to markup, but the controls themselves remain and behave the same.</p>
<h2>Control states and more</h2>
</div>
<p>Bootstrap's forms include styles for all the base form controls like input, textarea, and select you'd expect. But it also comes with a number of custom components like appended and prepended inputs and support for lists of checkboxes.</p>
<divclass="span4">
<p>States like error, warning, and success are included for each type of form control. Also included are styles for disabled controls.</p>
<h2>Control states and more</h2>
<p>Bootstrap's forms include styles for all the base form controls like input, textarea, and select you'd expect. But it also comes with a number of custom components like appended and prepended inputs and support for lists of checkboxes.</p>
<p>States like error, warning, and success are included for each type of form control. Also included are styles for disabled controls.</p>
</div>
</div>
<h2>Four types of forms</h2>
<h2>Four types of forms</h2>
<p>Bootstrap provides simple markup and styles for four styles of common web forms.</p>
<p>Bootstrap provides simple markup and styles for four styles of common web forms.</p>
...
@@ -839,19 +835,17 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -839,19 +835,17 @@ For example, <code>section</code> should be wrapped as inline.
<h2>Example forms <small>using just form controls, no extra markup</small></h2>
<h2>Example forms <small>using just form controls, no extra markup</small></h2>
<divclass="row">
<h3>Basic form</h3>
<divclass="span6">
<p>Smart and lightweight defaults without extra markup.</p>
<h3>Basic form</h3>
<formclass="well">
<p>Smart and lightweight defaults without extra markup.</p>
<p>Given the above example form layout, here's the markup associated with the first input and control group. The <code>.control-group</code>, <code>.control-label</code>, and <code>.controls</code> classes are all required for styling.</p>
</fieldset>
</form>
<h3>Example markup</h3>
<p>Given the above example form layout, here's the markup associated with the first input and control group. The <code>.control-group</code>, <code>.control-label</code>, and <code>.controls</code> classes are all required for styling.</p>
<preclass="prettyprint linenums">
<preclass="prettyprint linenums">
<form class="form-horizontal">
<form class="form-horizontal">
<fieldset>
<fieldset>
...
@@ -995,253 +982,241 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -995,253 +982,241 @@ For example, <code>section</code> should be wrapped as inline.
</fieldset>
</fieldset>
</form>
</form>
</pre>
</pre>
</div>
</div>
<br>
<br>
<h2>Form control states</h2>
<h2>Form control states</h2>
<divclass="row">
<p>Bootstrap features styles for browser-supported focused and <code>disabled</code> states. We remove the default Webkit <code>outline</code> and apply a <code>box-shadow</code> in its place for <code>:focus</code>.</p>
<divclass="span4">
<hr>
<p>Bootstrap features styles for browser-supported focused and <code>disabled</code> states. We remove the default Webkit <code>outline</code> and apply a <code>box-shadow</code> in its place for <code>:focus</code>.</p>
<h3>Form validation</h3>
<hr>
<p>It also includes validation styles for errors, warnings, and success. To use, add the error class to the surrounding <code>.control-group</code>.</p>
<h3>Form validation</h3>
<p>It also includes validation styles for errors, warnings, and success. To use, add the error class to the surrounding <code>.control-group</code>.</p>
<p>Input groups—with appended or prepended text—provide an easy way to give more context for your inputs. Great examples include the @ sign for Twitter usernames or $ for finances.</p>
<h3>Prepend & append inputs</h3>
<hr>
<p>Input groups—with appended or prepended text—provide an easy way to give more context for your inputs. Great examples include the @ sign for Twitter usernames or $ for finances.</p>
<h3>Checkboxes and radios</h3>
<hr>
<p>Up to v1.4, Bootstrap required extra markup around checkboxes and radios to stack them. Now, it's a simple matter of repeating the <code><label class="checkbox"></code> that wraps the <code><input type="checkbox"></code>.</p>
<h3>Checkboxes and radios</h3>
<p>Inline checkboxes and radios are also supported. Just add <code>.inline</code> to any <code>.checkbox</code> or <code>.radio</code> and you're done.</p>
<p>Up to v1.4, Bootstrap required extra markup around checkboxes and radios to stack them. Now, it's a simple matter of repeating the <code><label class="checkbox"></code> that wraps the <code><input type="checkbox"></code>.</p>
<hr>
<p>Inline checkboxes and radios are also supported. Just add <code>.inline</code> to any <code>.checkbox</code> or <code>.radio</code> and you're done.</p>
<h4>Inline forms and append/prepend</h4>
<hr>
<p>To use prepend or append inputs in an inline form, be sure to place the <code>.add-on</code> and <code>input</code> on the same line, without spaces.</p>
<h4>Inline forms and append/prepend</h4>
<hr>
<p>To use prepend or append inputs in an inline form, be sure to place the <code>.add-on</code> and <code>input</code> on the same line, without spaces.</p>
<h4>Form help text</h4>
<hr>
<p>To add help text for your form inputs, include inline help text with <code><span class="help-inline"></code> or a help text block with <code><p class="help-block"></code> after the input element.</p>
<h4>Form help text</h4>
<p>To add help text for your form inputs, include inline help text with <code><span class="help-inline"></code> or a help text block with <code><p class="help-block"></code> after the input element.</p>
<pclass="help-block">You may also use static classes that don't map to the grid, adapt to the responsive CSS styles, or account for varying types of controls (e.g., <code>input</code> vs. <code>select</code>).</p>
<pclass="help-block">You may also use static classes that don't map to the grid, adapt to the responsive CSS styles, or account for varying types of controls (e.g., <code>input</code> vs. <code>select</code>).</p>
@@ -1299,48 +1274,44 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -1299,48 +1274,44 @@ For example, <code>section</code> should be wrapped as inline.
</tbody>
</tbody>
</table>
</table>
<divclass="row">
<h3>Buttons for actions</h3>
<divclass="span4">
<p>As a convention, buttons should only be used for actions while hyperlinks are to be used for objects. For instance, "Download" should be a button while "recent activity" should be a link.</p>
<h3>Buttons for actions</h3>
<p>Button styles can be applied to anything with the <code>.btn</code> class applied. However, typically you'll want to apply these to only <code><a></code> and <code><button></code> elements.</p>
<p>As a convention, buttons should only be used for actions while hyperlinks are to be used for objects. For instance, "Download" should be a button while "recent activity" should be a link.</p>
<h3>Cross browser compatibility</h3>
<p>Button styles can be applied to anything with the <code>.btn</code> class applied. However, typically you'll want to apply these to only <code><a></code> and <code><button></code> elements.</p>
<p>IE9 doesn't crop background gradients on rounded corners, so we remove it. Related, IE9 jankifies disabled <code>button</code> elements, rendering text gray with a nasty text-shadow that we cannot fix.</p>
<h3>Cross browser compatibility</h3>
<p>IE9 doesn't crop background gradients on rounded corners, so we remove it. Related, IE9 jankifies disabled <code>button</code> elements, rendering text gray with a nasty text-shadow that we cannot fix.</p>
<h3>Multiple sizes</h3>
</div>
<p>Fancy larger or smaller buttons? Add <code>.btn-large</code>, <code>.btn-small</code>, or <code>.btn-mini</code> for two additional sizes.</p>
<p>For disabled buttons, add the <code>.disabled</code> class to links and the <code>disabled</code> attribute for <code><button></code> elements.</p>
<p>For disabled buttons, add the <code>.disabled</code> class to links and the <code>disabled</code> attribute for <code><button></code> elements.</p>
We use <code>.disabled</code> as a utility class here, similar to the common <code>.active</code> class, so no prefix is required.
<p>
</p>
<spanclass="label label-info">Heads up!</span>
We use <code>.disabled</code> as a utility class here, similar to the common <code>.active</code> class, so no prefix is required.
<h3>One class, multiple tags</h3>
</p>
<p>Use the <code>.btn</code> class on an <code><a></code>, <code><button></code>, or <code><input></code> element.</p>
</div>
<divclass="span4">
<h3>One class, multiple tags</h3>
<p>Use the <code>.btn</code> class on an <code><a></code>, <code><button></code>, or <code><input></code> element.</p>
<form>
<form>
<aclass="btn"href="">Link</a>
<aclass="btn"href="">Link</a>
<buttonclass="btn"type="submit">Button</button>
<buttonclass="btn"type="submit">Button</button>
...
@@ -1357,9 +1328,8 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -1357,9 +1328,8 @@ For example, <code>section</code> should be wrapped as inline.
<input class="btn" type="submit"
<input class="btn" type="submit"
value="Submit">
value="Submit">
</pre>
</pre>
<p>As a best practice, try to match the element for you context to ensure matching cross-browser rendering. If you have an <code>input</code>, use an <code><input type="submit"></code> for your button.</p>
<p>As a best practice, try to match the element for you context to ensure matching cross-browser rendering. If you have an <code>input</code>, use an <code><input type="submit"></code> for your button.</p>
</div>
</div>
</section>
</section>
...
@@ -1371,7 +1341,7 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -1371,7 +1341,7 @@ For example, <code>section</code> should be wrapped as inline.
<h1>Icons <small>Graciously provided by <ahref="http://glyphicons.com"target="_blank">Glyphicons</a></small></h1>
<h1>Icons <small>Graciously provided by <ahref="http://glyphicons.com"target="_blank">Glyphicons</a></small></h1>
</div>
</div>
<divclass="row">
<divclass="row">
<divclass="span3">
<divclass="span2">
<ulclass="the-icons">
<ulclass="the-icons">
<li><iclass="icon-glass"></i> icon-glass</li>
<li><iclass="icon-glass"></i> icon-glass</li>
<li><iclass="icon-music"></i> icon-music</li>
<li><iclass="icon-music"></i> icon-music</li>
...
@@ -1410,7 +1380,7 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -1410,7 +1380,7 @@ For example, <code>section</code> should be wrapped as inline.
@@ -1531,99 +1501,91 @@ For example, <code>section</code> should be wrapped as inline.
...
@@ -1531,99 +1501,91 @@ For example, <code>section</code> should be wrapped as inline.
<br>
<br>
<divclass="row">
<divclass="span4">
<h3>Built as a sprite</h3>
<h3>Built as a sprite</h3>
<p>Instead of making every icon an extra request, we've compiled them into a sprite—a bunch of images in one file that uses CSS to position the images with <code>background-position</code>. This is the same method we use on Twitter.com and it has worked well for us.</p>
<p>Instead of making every icon an extra request, we've compiled them into a sprite—a bunch of images in one file that uses CSS to position the images with <code>background-position</code>. This is the same method we use on Twitter.com and it has worked well for us.</p>
<p>All icons classes are prefixed with <code>.icon-</code> for proper namespacing and scoping, much like our other components. This will help avoid conflicts with other tools.</p>
<p>All icons classes are prefixed with <code>.icon-</code> for proper namespacing and scoping, much like our other components. This will help avoid conflicts with other tools.</p>
<p><ahref="http://glyphicons.com"target="_blank">Glyphicons</a> has granted us use of the Halflings set in our open-source toolkit so long as we provide a link and credit here in the docs. Please consider doing the same in your projects.</p>
<p><ahref="http://glyphicons.com"target="_blank">Glyphicons</a> has granted us use of the Halflings set in our open-source toolkit so long as we provide a link and credit here in the docs. Please consider doing the same in your projects.</p>
</div>
<h3>How to use</h3>
<divclass="span4">
<p>Bootstrap uses an <code><i></code> tag for all icons, but they have no case class—only a shared prefix. To use, place the following code just about anywhere:</p>
<h3>How to use</h3>
<p>Bootstrap uses an <code><i></code> tag for all icons, but they have no case class—only a shared prefix. To use, place the following code just about anywhere:</p>
<preclass="prettyprint linenums">
<preclass="prettyprint linenums">
<i class="icon-search"></i>
<i class="icon-search"></i>
</pre>
</pre>
<p>There are also styles available for inverted (white) icons, made ready with one extra class:</p>
<p>There are also styles available for inverted (white) icons, made ready with one extra class:</p>
<p>There are 140 classes to choose from for your icons. Just add an <code><i></code> tag with the right classes and you're set. You can find the full list in <strong>sprites.less</strong> or right here in this document.</p>
<p>There are 140 classes to choose from for your icons. Just add an <code><i></code> tag with the right classes and you're set. You can find the full list in <strong>sprites.less</strong> or right here in this document.</p>
<p>
<p>
<spanclass="label label-info">Heads up!</span>
<spanclass="label label-info">Heads up!</span>
When using beside strings of text, as in buttons or nav links, be sure to leave a space after the <code><i></code> tag for proper spacing.
When using beside strings of text, as in buttons or nav links, be sure to leave a space after the <code><i></code> tag for proper spacing.
</p>
</p>
<h3>Use cases</h3>
<p>Icons are great, but where would one use them? Here are a few ideas:</p>
<ul>
<li>As visuals for your sidebar navigation</li>
<li>For a purely icon-driven navigation</li>
<li>For buttons to help convey the meaning of an action</li>
<li>With links to share context on a user's destination</li>
</ul>
<p>Essentially, anywhere you can put an <code><i></code> tag, you can put an icon.</p>
<h3>Examples</h3>
<p>Use them in buttons, button groups for a toolbar, navigation, or prepended form inputs.</p>
<p>{{_i}}The best part about forms in Bootstrap is that all your inputs and controls look great no matter how you build them in your markup. No superfluous HTML is required, but we provide the patterns for those who require it.{{/i}}</p>
<p>{{_i}}The best part about forms in Bootstrap is that all your inputs and controls look great no matter how you build them in your markup. No superfluous HTML is required, but we provide the patterns for those who require it.{{/i}}</p>
<p>{{_i}}More complicated layouts come with succinct and scalable classes for easy styling and event binding, so you're covered at every step.{{/i}}</p>
<p>{{_i}}More complicated layouts come with succinct and scalable classes for easy styling and event binding, so you're covered at every step.{{/i}}</p>
</div>
<h2>{{_i}}Four layouts included{{/i}}</h2>
<divclass="span4">
<p>{{_i}}Bootstrap comes with support for four types of form layouts:{{/i}}</p>
<h2>{{_i}}Four layouts included{{/i}}</h2>
<ul>
<p>{{_i}}Bootstrap comes with support for four types of form layouts:{{/i}}</p>
<li>{{_i}}Vertical (default){{/i}}</li>
<ul>
<li>{{_i}}Search{{/i}}</li>
<li>{{_i}}Vertical (default){{/i}}</li>
<li>{{_i}}Inline{{/i}}</li>
<li>{{_i}}Search{{/i}}</li>
<li>{{_i}}Horizontal{{/i}}</li>
<li>{{_i}}Inline{{/i}}</li>
</ul>
<li>{{_i}}Horizontal{{/i}}</li>
<p>{{_i}}Different types of form layouts require some changes to markup, but the controls themselves remain and behave the same.{{/i}}</p>
</ul>
<p>{{_i}}Different types of form layouts require some changes to markup, but the controls themselves remain and behave the same.{{/i}}</p>
<h2>{{_i}}Control states and more{{/i}}</h2>
</div>
<p>{{_i}}Bootstrap's forms include styles for all the base form controls like input, textarea, and select you'd expect. But it also comes with a number of custom components like appended and prepended inputs and support for lists of checkboxes.{{/i}}</p>
<divclass="span4">
<p>{{_i}}States like error, warning, and success are included for each type of form control. Also included are styles for disabled controls.{{/i}}</p>
<h2>{{_i}}Control states and more{{/i}}</h2>
<p>{{_i}}Bootstrap's forms include styles for all the base form controls like input, textarea, and select you'd expect. But it also comes with a number of custom components like appended and prepended inputs and support for lists of checkboxes.{{/i}}</p>
<p>{{_i}}States like error, warning, and success are included for each type of form control. Also included are styles for disabled controls.{{/i}}</p>
</div>
</div>
<h2>{{_i}}Four types of forms{{/i}}</h2>
<h2>{{_i}}Four types of forms{{/i}}</h2>
<p>{{_i}}Bootstrap provides simple markup and styles for four styles of common web forms.{{/i}}</p>
<p>{{_i}}Bootstrap provides simple markup and styles for four styles of common web forms.{{/i}}</p>
...
@@ -770,19 +766,17 @@
...
@@ -770,19 +766,17 @@
<h2>{{_i}}Example forms <small>using just form controls, no extra markup</small>{{/i}}</h2>
<h2>{{_i}}Example forms <small>using just form controls, no extra markup</small>{{/i}}</h2>
<divclass="row">
<h3>{{_i}}Basic form{{/i}}</h3>
<divclass="span6">
<p>{{_i}}Smart and lightweight defaults without extra markup.{{/i}}</p>
<h3>{{_i}}Basic form{{/i}}</h3>
<formclass="well">
<p>{{_i}}Smart and lightweight defaults without extra markup.{{/i}}</p>
<p>{{_i}}Given the above example form layout, here's the markup associated with the first input and control group. The <code>.control-group</code>, <code>.control-label</code>, and <code>.controls</code> classes are all required for styling.{{/i}}</p>
</fieldset>
</form>
<h3>{{_i}}Example markup{{/i}}</h3>
<p>{{_i}}Given the above example form layout, here's the markup associated with the first input and control group. The <code>.control-group</code>, <code>.control-label</code>, and <code>.controls</code> classes are all required for styling.{{/i}}</p>
<preclass="prettyprint linenums">
<preclass="prettyprint linenums">
<form class="form-horizontal">
<form class="form-horizontal">
<fieldset>
<fieldset>
...
@@ -926,253 +913,241 @@
...
@@ -926,253 +913,241 @@
</fieldset>
</fieldset>
</form>
</form>
</pre>
</pre>
</div>
</div>
<br>
<br>
<h2>{{_i}}Form control states{{/i}}</h2>
<h2>{{_i}}Form control states{{/i}}</h2>
<divclass="row">
<p>{{_i}}Bootstrap features styles for browser-supported focused and <code>disabled</code> states. We remove the default Webkit <code>outline</code> and apply a <code>box-shadow</code> in its place for <code>:focus</code>.{{/i}}</p>
<divclass="span4">
<hr>
<p>{{_i}}Bootstrap features styles for browser-supported focused and <code>disabled</code> states. We remove the default Webkit <code>outline</code> and apply a <code>box-shadow</code> in its place for <code>:focus</code>.{{/i}}</p>
<h3>{{_i}}Form validation{{/i}}</h3>
<hr>
<p>{{_i}}It also includes validation styles for errors, warnings, and success. To use, add the error class to the surrounding <code>.control-group</code>.{{/i}}</p>
<h3>{{_i}}Form validation{{/i}}</h3>
<p>{{_i}}It also includes validation styles for errors, warnings, and success. To use, add the error class to the surrounding <code>.control-group</code>.{{/i}}</p>
<p>{{_i}}Input groups—with appended or prepended text—provide an easy way to give more context for your inputs. Great examples include the @ sign for Twitter usernames or $ for finances.{{/i}}</p>
<h3>{{_i}}Prepend & append inputs{{/i}}</h3>
<hr>
<p>{{_i}}Input groups—with appended or prepended text—provide an easy way to give more context for your inputs. Great examples include the @ sign for Twitter usernames or $ for finances.{{/i}}</p>
<h3>{{_i}}Checkboxes and radios{{/i}}</h3>
<hr>
<p>{{_i}}Up to v1.4, Bootstrap required extra markup around checkboxes and radios to stack them. Now, it's a simple matter of repeating the <code><label class="checkbox"></code> that wraps the <code><input type="checkbox"></code>.{{/i}}</p>
<h3>{{_i}}Checkboxes and radios{{/i}}</h3>
<p>{{_i}}Inline checkboxes and radios are also supported. Just add <code>.inline</code> to any <code>.checkbox</code> or <code>.radio</code> and you're done.{{/i}}</p>
<p>{{_i}}Up to v1.4, Bootstrap required extra markup around checkboxes and radios to stack them. Now, it's a simple matter of repeating the <code><label class="checkbox"></code> that wraps the <code><input type="checkbox"></code>.{{/i}}</p>
<hr>
<p>{{_i}}Inline checkboxes and radios are also supported. Just add <code>.inline</code> to any <code>.checkbox</code> or <code>.radio</code> and you're done.{{/i}}</p>
<h4>{{_i}}Inline forms and append/prepend{{/i}}</h4>
<hr>
<p>{{_i}}To use prepend or append inputs in an inline form, be sure to place the <code>.add-on</code> and <code>input</code> on the same line, without spaces.{{/i}}</p>
<h4>{{_i}}Inline forms and append/prepend{{/i}}</h4>
<hr>
<p>{{_i}}To use prepend or append inputs in an inline form, be sure to place the <code>.add-on</code> and <code>input</code> on the same line, without spaces.{{/i}}</p>
<h4>{{_i}}Form help text{{/i}}</h4>
<hr>
<p>{{_i}}To add help text for your form inputs, include inline help text with <code><span class="help-inline"></code> or a help text block with <code><p class="help-block"></code> after the input element.{{/i}}</p>
<h4>{{_i}}Form help text{{/i}}</h4>
<p>{{_i}}To add help text for your form inputs, include inline help text with <code><span class="help-inline"></code> or a help text block with <code><p class="help-block"></code> after the input element.{{/i}}</p>
<pclass="help-block">{{_i}}You may also use static classes that don't map to the grid, adapt to the responsive CSS styles, or account for varying types of controls (e.g., <code>input</code> vs. <code>select</code>).{{/i}}</p>
<pclass="help-block">{{_i}}You may also use static classes that don't map to the grid, adapt to the responsive CSS styles, or account for varying types of controls (e.g., <code>input</code> vs. <code>select</code>).{{/i}}</p>
<p>{{_i}}As a convention, buttons should only be used for actions while hyperlinks are to be used for objects. For instance, "Download" should be a button while "recent activity" should be a link.{{/i}}</p>
<h3>{{_i}}Buttons for actions{{/i}}</h3>
<p>{{_i}}Button styles can be applied to anything with the <code>.btn</code> class applied. However, typically you'll want to apply these to only <code><a></code> and <code><button></code> elements.{{/i}}</p>
<p>{{_i}}As a convention, buttons should only be used for actions while hyperlinks are to be used for objects. For instance, "Download" should be a button while "recent activity" should be a link.{{/i}}</p>
<h3>{{_i}}Cross browser compatibility{{/i}}</h3>
<p>{{_i}}Button styles can be applied to anything with the <code>.btn</code> class applied. However, typically you'll want to apply these to only <code><a></code> and <code><button></code> elements.{{/i}}</p>
<p>{{_i}}IE9 doesn't crop background gradients on rounded corners, so we remove it. Related, IE9 jankifies disabled <code>button</code> elements, rendering text gray with a nasty text-shadow that we cannot fix.{{/i}}</p>
<h3>{{_i}}Cross browser compatibility{{/i}}</h3>
<p>{{_i}}IE9 doesn't crop background gradients on rounded corners, so we remove it. Related, IE9 jankifies disabled <code>button</code> elements, rendering text gray with a nasty text-shadow that we cannot fix.{{/i}}</p>
<h3>{{_i}}Multiple sizes{{/i}}</h3>
</div>
<p>{{_i}}Fancy larger or smaller buttons? Add <code>.btn-large</code>, <code>.btn-small</code>, or <code>.btn-mini</code> for two additional sizes.{{/i}}</p>
<p>{{_i}}Fancy larger or smaller buttons? Add <code>.btn-large</code>, <code>.btn-small</code>, or <code>.btn-mini</code> for two additional sizes.{{/i}}</p>
<p>{{_i}}For disabled buttons, add the <code>.disabled</code> class to links and the <code>disabled</code> attribute for <code><button></code> elements.{{/i}}</p>
<p>{{_i}}For disabled buttons, add the <code>.disabled</code> class to links and the <code>disabled</code> attribute for <code><button></code> elements.{{/i}}</p>
<p>{{_i}}As a best practice, try to match the element for you context to ensure matching cross-browser rendering. If you have an <code>input</code>, use an <code><input type="submit"></code> for your button.{{/i}}</p>
<p>{{_i}}As a best practice, try to match the element for you context to ensure matching cross-browser rendering. If you have an <code>input</code>, use an <code><input type="submit"></code> for your button.{{/i}}</p>
</div>
</div>
</section>
</section>
...
@@ -1302,7 +1272,7 @@
...
@@ -1302,7 +1272,7 @@
<h1>{{_i}}Icons <small>Graciously provided by <ahref="http://glyphicons.com"target="_blank">Glyphicons</a></small>{{/i}}</h1>
<h1>{{_i}}Icons <small>Graciously provided by <ahref="http://glyphicons.com"target="_blank">Glyphicons</a></small>{{/i}}</h1>
<p>{{_i}}Instead of making every icon an extra request, we've compiled them into a sprite—a bunch of images in one file that uses CSS to position the images with <code>background-position</code>. This is the same method we use on Twitter.com and it has worked well for us.{{/i}}</p>
<p>{{_i}}Instead of making every icon an extra request, we've compiled them into a sprite—a bunch of images in one file that uses CSS to position the images with <code>background-position</code>. This is the same method we use on Twitter.com and it has worked well for us.{{/i}}</p>
<p>{{_i}}All icons classes are prefixed with <code>.icon-</code> for proper namespacing and scoping, much like our other components. This will help avoid conflicts with other tools.{{/i}}</p>
<p>{{_i}}All icons classes are prefixed with <code>.icon-</code> for proper namespacing and scoping, much like our other components. This will help avoid conflicts with other tools.{{/i}}</p>
<p>{{_i}}<ahref="http://glyphicons.com"target="_blank">Glyphicons</a> has granted us use of the Halflings set in our open-source toolkit so long as we provide a link and credit here in the docs. Please consider doing the same in your projects.{{/i}}</p>
<p>{{_i}}<ahref="http://glyphicons.com"target="_blank">Glyphicons</a> has granted us use of the Halflings set in our open-source toolkit so long as we provide a link and credit here in the docs. Please consider doing the same in your projects.{{/i}}</p>
</div>
<h3>{{_i}}How to use{{/i}}</h3>
<divclass="span4">
<p>{{_i}}Bootstrap uses an <code><i></code> tag for all icons, but they have no case class—only a shared prefix. To use, place the following code just about anywhere:{{/i}}</p>
<h3>{{_i}}How to use{{/i}}</h3>
<p>{{_i}}Bootstrap uses an <code><i></code> tag for all icons, but they have no case class—only a shared prefix. To use, place the following code just about anywhere:{{/i}}</p>
<preclass="prettyprint linenums">
<preclass="prettyprint linenums">
<i class="icon-search"></i>
<i class="icon-search"></i>
</pre>
</pre>
<p>{{_i}}There are also styles available for inverted (white) icons, made ready with one extra class:{{/i}}</p>
<p>{{_i}}There are also styles available for inverted (white) icons, made ready with one extra class:{{/i}}</p>
<p>{{_i}}There are 140 classes to choose from for your icons. Just add an <code><i></code> tag with the right classes and you're set. You can find the full list in <strong>sprites.less</strong> or right here in this document.{{/i}}</p>
<p>{{_i}}There are 140 classes to choose from for your icons. Just add an <code><i></code> tag with the right classes and you're set. You can find the full list in <strong>sprites.less</strong> or right here in this document.{{/i}}</p>
{{_i}}When using beside strings of text, as in buttons or nav links, be sure to leave a space after the <code><i></code> tag for proper spacing.{{/i}}
{{_i}}When using beside strings of text, as in buttons or nav links, be sure to leave a space after the <code><i></code> tag for proper spacing.{{/i}}
</p>
</p>
<h3>{{_i}}Use cases{{/i}}</h3>
<p>{{_i}}Icons are great, but where would one use them? Here are a few ideas:{{/i}}</p>
<ul>
<li>{{_i}}As visuals for your sidebar navigation{{/i}}</li>
<li>{{_i}}For a purely icon-driven navigation{{/i}}</li>
<li>{{_i}}For buttons to help convey the meaning of an action{{/i}}</li>
<li>{{_i}}With links to share context on a user's destination{{/i}}</li>
</ul>
<p>{{_i}}Essentially, anywhere you can put an <code><i></code> tag, you can put an icon.{{/i}}</p>
<h3>{{_i}}Examples{{/i}}</h3>
<p>{{_i}}Use them in buttons, button groups for a toolbar, navigation, or prepended form inputs.{{/i}}</p>