migration.md 10.7 KB
Newer Older
1
---
Mark Otto's avatar
Mark Otto committed
2
layout: docs
Mark Otto's avatar
Mark Otto committed
3
title: Migrating to v4
4
group: migration
5
6
---

7
8
Bootstrap 4 is a major rewrite of almost the entire project. The most notable changes are summarized immediately below, followed by more specific class and behavioral changes to relevant components.

Mark Otto's avatar
Mark Otto committed
9
10
11
12
{% callout info %}
**Heads up!** This will be in flux as work on the v4 alphas progresses. Until then consider it incomplete, and we'd love pull requests to help keep it up to date.
{% endcallout %}

Mark Otto's avatar
Mark Otto committed
13
## Summary
14

15
Here are the big ticket items you'll want to be aware of when moving from v3 to v4.
16

Mark Otto's avatar
Mark Otto committed
17
18
### Browser support

19
- Dropped IE8 and iOS 6 support. v4 is now only IE9+ and iOS 7+. For sites needing either of those, use v3.
20
- Added official support for Android v5.0 Lollipop's Browser and WebView. Earlier versions of the Android Browser and WebView remain only unofficially supported.
Mark Otto's avatar
Mark Otto committed
21
22
23

### Global changes

24
- Switched from [Less](http://lesscss.org/) to [SCSS](http://sass-lang.com/) for our source CSS files.
25
- Switched from `px` to `rem` as our primary CSS unit.
26
27
- Global font-size increased from `14px` to `16px`.
- Added a new grid tier for ~`480px` and below.
28
- Replaced the separate optional theme with configurable options via SCSS variables (e.g., `$enable-gradients: true`).
Mark Otto's avatar
Mark Otto committed
29
30
31
32

### Components

- Dropped panels, thumbnails, and wells for a new all-encompassing component, cards.
33
34
35
36
- Dropped the Glyphicons icon font. If you need icons, some options are:
  - the upstream version of [Glyphicons](http://glyphicons.com/)
  - [Octicons](https://octicons.github.com/)
  - [Font Awesome](https://fortawesome.github.io/Font-Awesome/)
37
- Dropped the Affix jQuery plugin. We recommend using a `position: sticky` polyfill instead. [See the HTML5 Please entry](http://html5please.com/#sticky) for details and specific polyfill recommendations.
38
  - If you were using Affix to apply additional, non-`position` styles, the polyfills might not support your use case. One option for such uses is the third-party [ScrollPos-Styler](https://github.com/acch/scrollpos-styler) library.
39
- Refactored nearly all components to use more unnested classes instead of children selectors.
Mark Otto's avatar
Mark Otto committed
40
41

### Misc
42
- Non-responsive usage of Bootstrap is no longer supported.
Mark Otto's avatar
Mark Otto committed
43
- Dropped the online Customizer in favor of more extensive setup documentation and customized builds.
44

45
## By component
46

Mark Otto's avatar
Mark Otto committed
47
48
49
50
51
52
53
54
55
56
57
58
This list highlights key changes by component between v3.x.x and v4.0.0.

### Reboot

New to Bootstrap 4 is the Reboot, a new stylesheet that builds on Normalize with our own somewhat opinionated reset styles. Selectors appearing in this file only use elements—there are no classes here. This isolates our reset styles from our component styles for a more modular approach. Some of the most important resets this includes are the `box-sizing: border` change, moving from `rem` to `em` units on many elements, link styles, and many form element resets.

### Typography

- Moved all `.text-` utilities to the `_utilities.scss` file.
- Dropped the `.page-header` class entirely.
- `.dl-horizontal` now requires grid classes, increasing flexbility in column widths.
- Custom `<blockquote>` styling has moved to classes—`.blockquote` and the `.blockquote-reverse` modifier.
59

60
61
62
63
### Images

- Renamed `.img-responsive` to `.img-fluid`.

64
65
66
67
### Tables

- Nearly all instances of the `>` selector have been removed, meaning nested tables will now automatically inherit styles from their parents. This greatly simplifies our selectors and potential customizations.
- Responsive tables no longer require a wrapping element. Instead, just put the `.table-responsive` right on the `<table>`.
Mark Otto's avatar
Mark Otto committed
68
- Renamed `.table-condensed` to `.table-sm` for consistency.
69
- Added a new `.table-inverse` option.
70
71
- Added a new `.table-reflow` option.
- Added table header modifers: `.thead-default` and `.thead-inverse`
72

Mark Otto's avatar
Mark Otto committed
73
74
75
### Forms

- Moved element resets to the `_reboot.scss` file.
76
- Renamed `.control-label` to `.form-control-label`.
Mark Otto's avatar
Mark Otto committed
77
78
- Renamed `.input-lg` and `.input-sm` to `.form-control-lg` and `.form-control-sm`, respectively.
- Dropped `.form-group-*` classes for simplicity's sake. Use `.form-control-*` classes instead now.
79
80
81
82
- Horizontal forms overhauled:
  - Dropped the `.form-horizontal` class requirement.
  - `.form-group` no longer mixins the `.row` class, so it's now required for grid layouts.
  - Added new `.form-control-label` class to vertically center labels with `.form-control`s.
Mark Otto's avatar
Mark Otto committed
83

84
85
### Buttons

86
- Renamed `.btn-default` to `.btn-secondary`.
87
- Dropped the `.btn-xs` class entirely.
88
89
- The [stateful button](http://getbootstrap.com/javascript/#buttons-methods) feature of the `button.js` jQuery plugin has been dropped. This includes the `$().button(string)` and `$().button('reset')` methods. We advise using a tiny bit of custom JavaScript instead, which will have the benefit of behaving exactly the way you want it to.
  - Note that the other features of the plugin (button checkboxes, button radios, single-toggle buttons) have been retained in v4.
90

Mark Otto's avatar
Mark Otto committed
91
92
93
94
### Grid system

- Added a new `~480px` grid breakpoint, meaning there are now five total tiers.

95
96
97
98
### Button group

- Dropped the `.btn-group-xs` class entirely.

Mark Otto's avatar
Mark Otto committed
99
100
101
102
103
### Navs

- Dropped nearly all `>` selectors for simpler styling via un-nested classes.
- Instead of HTML-specific selectors like `.nav > li > a`, we use separate classes for `.nav`s, `.nav-item`s, and `.nav-link`s. This makes your HTML more flexible while bringing along increased extensibility.

104
### Navbar
105
106
107

- Dropped the `.navbar-form` class entirely. It's no longer necessary.

108
109
### Pager

Mark Otto's avatar
Mark Otto committed
110
111
112
113
114
- Renamed `.previous` and `.next` to `.pager-prev` and `.pager-next`.

### Panels, thumbnails, and wells

Dropped entirely for the new card component.
115

116
117
118
119
120
121
122
123
124
125
126
127
128
129
#### Panels

- `.panel` to `.card`
- `.panel-default` removed and no replacement
- `.panel-heading` to `.card-header`
- `.panel-title` to `.card-title`
- `.panel-body` to `.card-block`
- `.panel-footer` to `.card-footer`
- `.panel-primary` to `.card-primary` and `.card-inverse`
- `.panel-success` to `.card-success` and `.card-inverse`
- `.panel-info` to `.card-info` and `.card-inverse`
- `.panel-warning` to `.card-warning` and `.card-inverse`
- `.panel-danger` to `.card-danger` and `.card-inverse`

130
131
### Carousel

Mark Otto's avatar
Mark Otto committed
132
- Renamed `.item` to `.carousel-item`.
133

134
135
### Utilities

136
137
- Added `.pull-{xs,sm,md,lg,xl}-{left,right,none}` classes for responsive floats
- Removed `.pull-left` and `.pull-right` since they're redundant to `.pull-xs-left` and `.pull-xs-right`
138

139
140
## Documentation

Mark Otto's avatar
Mark Otto committed
141
Our documentation received an upgrade across the board as well. Here's the low down:
142

Mark Otto's avatar
Mark Otto committed
143
144
145
- We're still using Jekyll, but we have custom plugins in the mix:
  - `example.rb` is a fork of the default `highlight.rb` plugin, allowing for easier example-code handling.
  - `callout.rb` is a similar fork of that, but designed for our special docs callouts.
146
147
148
- All docs content has been rewritten in Markdown (instead of HTML) for easier editing.
- Pages have been reorganized for simpler content and a more approachable hierarchy.
- We moved from regular CSS to SCSS to take full advantage of Bootstrap's variables, mixins, and more.
149
150

## What's new
151

152
153
We've added new components and changed some existing ones. Here are the new or updated styles.

154
155
156
157
| Component | Description |
| --- | --- |
| Cards | New, more flexible component to replace v3's panels, thumbnails, and wells. |
| New navbar | Replaces the previous navbar with a new, simpler component. |
158
| New progress bars | Replaces the old `.progress` `<div>` with a real `<progress>` element. |
159
| New table variants | Adds `.table-inverse`, table head options, replaces `.table-condensed` with `.table-sm`, and `.table-reflow`. |
160
| New utility classes | |
161

162
163
TODO: audit new classes that didn't exist in v3

164
165
166
## What's removed
The following components have been removed in v4.0.0.

167
168
| Component | Removed from 3.x.x | 4.0.0 Equivalent |
| --- | --- | --- |
169
170
171
| Panels |  | Cards |
| Thumbnails |  | Cards |
| Wells |  | Cards |
172
| Justified navs | | |
173

174
TODO: audit classes in v3 that aren't present in v4
175

176
177
### Responsive utilities

Mark Otto's avatar
Mark Otto committed
178
The following deprecated variables have been removed in v4.0.0:
179

180
181
182
183
* `@screen-phone`, `@screen-tablet`, `@screen-desktop`, `@screen-lg-desktop`. Use the more abstract `$screen-{xs,sm,md,lg,xl}-*` variables instead.
* `@screen-sm`, `@screen-md`, `@screen-lg`. Use the more clearly named `$screen-{xs,sm,md,lg,xl}-min` variables instead.
* `@screen-xs`, `@screen-xs-min`. The extra small breakpoint has no lower bound, so these variables were logically absurd. Reformulate your expression in terms of `$screen-xs-max` instead.

Mark Otto's avatar
Mark Otto committed
184
185
186
187
188
189
190
191
192
193
The responsive utility classes have also been overhauled.

- The old classes (`.hidden-xs` `.hidden-sm` `.hidden-md` `.hidden-lg` `.visible-xs-block` `.visible-xs-inline` `.visible-xs-inline-block` `.visible-sm-block` `.visible-sm-inline` `.visible-sm-inline-block` `.visible-md-block` `.visible-md-inline` `.visible-md-inline-block` `.visible-lg-block` `.visible-lg-inline` `.visible-lg-inline-block`) are gone.
- They have been replaced by `.hidden-xs-up` `.hidden-xs-down` `.hidden-sm-up` `.hidden-sm-down` `.hidden-md-up` `.hidden-md-down` `.hidden-lg-up` `.hidden-lg-down`.
- The `.hidden-*-up` classes hide the element when the viewport is at the given breakpoint or larger (e.g. `.hidden-md-up` hides an element on medium, large, and extra-large devices).
- The `.hidden-*-down` classes hide the element when the viewport is at the given breakpoint or smaller (e.g. `.hidden-md-down` hides an element on extra-small, small, and medium devices).

Rather than using explicit `.visible-*` classes, you make an element visible by simply not hiding it at that screen size. You can combine one `.hidden-*-up` class with one `.hidden-*-down` class to show an element only on a given interval of screen sizes (e.g. `.hidden-sm-down.hidden-xl-up` shows the element only on medium and large devices).

Note that the changes to the grid breakpoints in v4 means that you'll need to go one breakpoint larger to achieve the same results (e.g. `.hidden-md` is more similar to `.hidden-lg-down` than to `.hidden-md-down`). The new responsive utility classes don't attempt to accommodate less common cases where an element's visibility can't be expressed as a single contiguous range of viewport sizes; you will instead need to use custom CSS in such cases.
194

Mark Otto's avatar
Mark Otto committed
195
196
197
## Misc notes to prioritize

- Removed the `min--moz-device-pixel-ratio` typo hack for retina media queries
198
- Dropped `.hidden` and `.show` because they conflict with jQuery's `$(...).hide()` and `$(...).show()` methods.
Mark Otto's avatar
Mark Otto committed
199
200
- Change buttons' `[disabled]` to `:disabled` as IE9+ supports `:disabled`. However `fieldset[disabled]` is still necessary because [native disabled fieldsets are still buggy in IE11](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset#Browser_compatibility).

201
202
TODO: audit list of stuff in v3 that was marked as deprecated

203
## Additional notes
204
- Removed support for styled nested tables (for now)