21 merge requests!7033Fix backdrop undefined bug in modal,!8635ignore Gruntfile.js in jekyll,!8339Fix broken links to navbar component in docs examples,!7329Fix for issue #7328,!7219Fix for mini typo mistake in css.html,!7674Clear float on all when navbar is collapsed - v3,!7344Fixed .spanX selector (*= instead of ^=),!7346Fix compilation error,!7775added some tests for tooltip title setter,!8157Close Me: Docs "Customize and Download" button fix,!7509Proposed fix for allowing Collapse events ('show'/'hide') to be cancelled,!7964commit fixes #7792,!8656Added rel="stylesheet" to CDN-Examples,!8527Inner properties move 1,!8245Interactive color picker - Closed: request against wrong branch,!7865Patch 2,!7651Drop the sizzle dependency to allow smaller builds targeting mobile devices,!6853typeahead: do not store item data in an attribute,!6666Patch 1,!65463.0.0 wip - fixed the issue in which the test pid isn't killed if a test fails,!6503control markup changes added
@@ -1650,13 +1650,17 @@ For example, <code><section></code> should be wrapped as inlin
</pre>
<h3>Disabled fieldsets</h3>
<p>Add the <code>disabled</code> attribute on a <code>fieldset</code> to disable all the controls within the fieldset at once.</p>
<p>Add the <code>disabled</code> attribute to a <code><fieldset></code> to disable all the controls within the <code><fieldset></code> at once. Link buttons (with the <code><a></code> element) will be aesthetically disabled, but you will need custom JavaScript to disable their behavior.</p>
<formclass="bs-docs-example form-inline">
<fieldsetdisabled>
<inputtype="text"class="span4"placeholder="These controls are all disabled just">
<selectclass="span4">
<option>by being under a disabled fieldset</option>
<option>by being under a disabled fieldset</option>
<option>Disabled select</option>
</select>
<div class="checkbox">
<label>
...
...
@@ -1681,11 +1685,6 @@ For example, <code><section></code> should be wrapped as inlin
</fieldset>
</form>
</pre>
<p>
<spanclass="label label-info">Heads up!</span>
Contrary to the HTML5 spec, form controls within a <code>fieldset</code>'s <code>legend</code> will also be disabled.<br>
Also, <code><a></code> buttons within a <code>fieldset[disabled]</code> will be styled like they each had the <code>.disabled</code> class, but this only affects aesthetics; you must use custom JavaScript to actually make such links non-functional.
</p>
<h3>Validation states</h3>
<p>Bootstrap includes validation styles for error, warning, info, and success messages. To use, add the appropriate class to the surrounding <code>.control-group</code>.</p>
@@ -1590,13 +1590,17 @@ For example, <code><section></code> should be wrapped as inlin
</pre>
<h3>Disabled fieldsets</h3>
<p>Add the <code>disabled</code> attribute on a <code>fieldset</code> to disable all the controls within the fieldset at once.</p>
<p>Add the <code>disabled</code> attribute to a <code><fieldset></code> to disable all the controls within the <code><fieldset></code> at once. Link buttons (with the <code><a></code> element) will be aesthetically disabled, but you will need custom JavaScript to disable their behavior.</p>
<formclass="bs-docs-example form-inline">
<fieldsetdisabled>
<inputtype="text"class="span4"placeholder="These controls are all disabled just">
<selectclass="span4">
<option>by being under a disabled fieldset</option>
<option>by being under a disabled fieldset</option>
<option>Disabled select</option>
</select>
<div class="checkbox">
<label>
...
...
@@ -1621,11 +1625,6 @@ For example, <code><section></code> should be wrapped as inlin
</fieldset>
</form>
</pre>
<p>
<spanclass="label label-info">Heads up!</span>
Contrary to the HTML5 spec, form controls within a <code>fieldset</code>'s <code>legend</code> will also be disabled.<br>
Also, <code><a></code> buttons within a <code>fieldset[disabled]</code> will be styled like they each had the <code>.disabled</code> class, but this only affects aesthetics; you must use custom JavaScript to actually make such links non-functional.
</p>
<h3>Validation states</h3>
<p>Bootstrap includes validation styles for error, warning, info, and success messages. To use, add the appropriate class to the surrounding <code>.control-group</code>.</p>