- 30 Oct, 2016 10 commits
-
-
Catalin Zalog authored
Firefox requires a width and flex-basis value to size the input field correctly. Despite the width being 1%, the input will size correctly at all parent widths. http://codepen.io/zalog/pen/bpMJmv
-
Mark Otto authored
floated content has to come first in the DOM, otherwise you can get alignment bugs. in flexbox though, that's not the case. as such, i'm adding this example code to guide folks to the changes needed to move between default and flex modes.
-
https://github.com/rosskevin/bootstrapMark Otto authored
Merge branch 'v4-flex-list-group' of https://github.com/rosskevin/bootstrap into rosskevin-v4-flex-list-group
-
Mark Otto authored
-
-
Mark Otto authored
-
Valentine Abanosimov authored
-
Valentine Abanosimov authored
-
Valentine Abanosimov authored
-
- 29 Oct, 2016 2 commits
- 28 Oct, 2016 24 commits
-
-
Mark Otto authored
-
Mark Otto authored
-
Mark Otto authored
-
Mark Otto authored
-
-
Mark Otto authored
Alphabetized carousel options & added "ride" to it
-
Mark Otto authored
Zero out the default margin-bottom on label.custom-file
-
Mark Otto authored
Re-use 'between' mixin for 'only' mixin
-
Mark Otto authored
-
Mark Otto authored
-
Mark Otto authored
Add some properties to the list of property order in .scss-lint.yml
-
Mark Otto authored
Visibility mixin
-
Mark Otto authored
Proper input group sizing and alignment in flexbox mode
-
Mark Otto authored
Add a min-height: 1.5rem; to custom controls
-
Mark Otto authored
Calculcate the top offset for custom control indicators
-
Mark Otto authored
-
Mark Otto authored
-
Mark Otto authored
-
-
Mark Otto authored
Remove hard-coded value in button-outline-variant
-
Mark Otto authored
cleaned up the docs to complete the change from .tag to .badge
-
Mark Otto authored
-
- 27 Oct, 2016 4 commits
-
-
judetucker authored
-
Mark Otto authored
Fixes #20730. This change computes the minimum needed height of what a single line of text would be for the custom checkboxes/radios. This is required because our custom control indicators are positioned absolutely, meaning they cannot be clearfixed or anything like that. Using a computed value means it should scale nicely in case of customization
-
Mark Otto authored
-