The Bootstrap Blog

News and announcements for all things Bootstrap, including new releases, Bootstrap Themes, and Bootstrap Icons.

Bootstrap 3.4.0

@mdo December 13, 2018

That’s not a typo—today we’re shipping Bootstrap 3.4.0, a long overdue update to address some quality of life issues, XSS fixes, and build tooling updates to make it easier for us, and you, to develop.

While we’d planned for ages to do a fresh v3.x update, we lost steam as energy was focused on all the work in v4. Early this year, one issue in particular gained a ton of momentum from the community and the core team decided to do a huge push to pull together a solid release. I regret the time it took to pull this release together, especially given the security fixes, but with the improvements under the hood, v3 has never been easier to develop and maintain. Thanks for your continued support along the way!

Keep reading for what’s changed and a look ahead at what’s coming in v4.2.0.

What’s new

While we haven’t publicly worked on v3.x in years, we’ve heard from all of you during that time that we needed to do a new release to address

  • New: Added a .row-no-gutters class.
  • New: Added docs searching via Algolia.
  • Fixed: Resolved an XSS issue in Alert, Carousel, Collapse, Dropdown, Modal, and Tab components. See https://snyk.io/vuln/npm:bootstrap:20160627 for details.
  • Fixed: Added padding to .navbar-fixed-* on modal open
  • Fixed: Removed the double border on <abbr> elements.
  • Removed Gist creation in web-based Customizer since anonymous gists were disabled long ago by GitHub.
  • Removed drag and drop support from Customizer since it didn’t work anymore.

Our documentation and tooling saw massive updates as well to make it easier to work on v3.x, for ourselves and for you.

  • Added a dropdown to the docs nav for newer and previous versions.
  • Update the docs to use a new baseurl, /docs/3.4/, to version the v3.x documentation like we do with v4.
  • Reorganized the v3 docs CSS to use Less.
  • Switched to BrowserStack for tests.
  • Updated links to always use https and fix broken URLs.
  • Replaced ZeroClipboard with clipboard.js

Head to the Bootstrap 3.4 docs to see the latest in action. Check out the v3.4.0 pull request for even more context on what’s changed.

Upgrading

Upgrade your Bootstrap 3 projects to v3.4.0 with npm i bootstrap@previous or npm i bootstrap@3.4.0. This release won’t be available via Bower to start given the package manager was deprecated and has largely been unused by us in v4 for well over a year. Stay tuned for CDN and Rubygem updates.

Open Collective

Also new with our v3.4 is the creation of an Open Collective page to help support the maintainers contributing to Bootstrap. The team has been very excited about this as a way to be transparent about maintainer costs (both time and money), as well as recognition of efforts.

v4.2 and beyond

We’ve been working on a huge v4.2 update for several months now. Our attention has largely been on advancing the project and simplifying it’s dependencies, namely by removing our jQuery dependency. That work has sparked a keen interest in a moderately scoped v5 release, so we’ve been taking our sweet time with v4.2 to sneak in as many new features as we can.

After we ship v4.2, we’ll plan for point releases to address any bugs and improvements as y’all start to use the new version. From there, we’ll start to share more plans on v5 to remove jQuery, drop support for older browsers, and clear up some cruft. This won’t be a sweeping rewrite, but rather an iterative improvement on v4. Stay tuned!

Bootstrap 4.1.3

@mdo July 24, 2018

Hot on the heels of v4.1.2, we’re shipping another patch release to address an issue with our browserslist config, fix some CSS bugs, make JavaScript plugins UMD ready, and improve form control rendering. Up next will be v4.2, our second minor release where we add some new features.

But first, here are the highlights for v4.1.3. Pay attention to the change to .form-controls which adds a new fixed height.

  • Fixed: Moved the browserslist config from our package.json to a separate file to avoid unintended inherited browser settings across npm projects.
  • Fixed: Removed the :not(:root) selector from our svg Reboot styles, resolving an issue that caused all inline SVGs ignore vertical-align styles via single class due to higher specificity.
  • Fixed: Buttons in custom file inputs are once again clickable when focused.
  • Improved: Bootstrap’s plugins can now be imported separately in any contexts because they are now UMD ready.
  • Improved: .form-controls now have a fixed height to compensate for differences in computed height across different types. This also fixes some IE alignment issues.
  • Improved: Added Noto Color Emoji to our system font stack for better rendering in Linux OSes.

Checkout the full v4.1.3 ship list and GitHub project for the full details. Up next is v4.2, so stay tuned for some awesome new features like toasts, dismissible badges, negative margins (responsive grid gutters!), spinners, and more!

Head to the v4.1.x docs to see the latest in action. The full release has been published to npm and will soon appear on the Bootstrap CDN and Rubygems.

Bootstrap 4.1.2

@mdo July 12, 2018

We’ve been busy these last couple months since launching v4.1.1, but we’re back with another bug fix and some sweeping changes to how we build and publish our docs after the issues stemming from our v4.1.x launches.

When we launched v4.1, we ran into unexpected issues with having to rearrange asset paths after deploying, resulting in broken image URLs, a busted service worker, and more. Since then, we’re ironed out most of the kinks and introduced a new docs directory structure inside the repo. Nothing should change for anyone using our docs, but those contributing to the project and developing locally may need to rebase their changes or update their branches accordingly.

Beyond the file structure changes, here are the highlights for v4.1.2:

  • Fixed an XSS vulnerability in tooltip, collapse, and scrollspy plugins
  • Improved how we query elements in our JavaScript plugins
  • Inline SVGs now have the same vertical alignment as images
  • Fixed issues with double transitions on carousels
  • Added Edge and IE10-11 fallbacks to our floating labels example
  • Various improvements to form controls, including disabled states on file inputs and unified focus styles for selects
  • Miscellaneous build tool improvements and documentation fixes

Checkout the full v4.1.2 ship list and GitHub project for the full details. Up next will either be v4.1.3 or v4.2 depending on how smoothly this release goes and how well we can keep up with reviewing and merging pull requests.

Head to the v4.1.x docs to see the latest in action. The full release has been published to npm and will soon appear on the Bootstrap CDN and Rubygems.

Bootstrap 4.1.1

@mdo April 30, 2018

We’re a few weeks out from v4.1 and we have our first patch release of Bootstrap 4! It’s a straightforward set of bug fixes and build tool quality of life updates.

Here’s a quick rundown of some of the changes:

  • Added validation styles for file inputs
  • Improved printing of dark tables
  • Suppressed that text-hide deprecation notice by default
  • Fixed an issue where Collapse wasn’t working in Internet Explorer
  • Cleaned up some JS globals and improve coverage
  • Bumped dependencies, namely Jekyll
  • Fixed docs issue with incorrect name for our monospace font utility

Checkout the full v4.1.1 ship list and GitHub project for the full details. Up next will be v4.1.2, another patch release to address the next set of CSS and JS bugs you’ve help share with us since v4 launched.

Bootstrap 4.1

@mdo April 09, 2018

Two months ago we shipped the first major release of Bootstrap 4 and we’re thrilled y’all love the latest release and our brand new themes so much. Today we’re shipping our first minor release, v4.1! This release comes later than expected and some of the fixes we intended, but there’s still a boatload of fixes, docs updates, build tool changes, and even a few small new features.

Updated docs URL

With the release of v4 stable, we moved to a versioned docs setup, meaning each minor release would bring with it a new hosted version of our docs. This allows folks who haven’t yet upgraded stick to the docs they know and love and avoids breaking URLs across the web. With today’s release, our we’ll have a new URL for this release’s documentation, getbootstrap.com/docs/4.1/. The previous URL, getbootstrap.com/docs/4.0/ will still work as y’all would imagine.

Highlights

Here’s what’s new in addition to our bug fixes and docs updates:

  • Added new custom range form control.
  • Added new .carousel-fade modifier to switch carousel from horizontal sliding to crossfade.
  • Added new .dropdown-item-text for plaintext dropdown items.
  • Added new .flex-fill, .flex-grow-*, and .flex-shrink-* utilities.
  • Added new .table-borderless variant for tables.
  • Added new .text-monospace utility.
  • Added new .text-body (default body color), .text-black-50 (50% opacity black), and .text-white-50 (50% opacity white) utilities.
  • Added new .shadow-* utilities for quickly adding box-shadows.
  • Added ability to disable Popper’s positioning in dropdowns.
  • Updated our Theming docs to confirm you cannot use CSS variables in media queries (sorry folks!).
  • Fixed longstanding issue with Chrome rendering CSS columns incorrectly for cards.
  • Deprecated .text-hide—you’ll see a warning during compilation—as it’s a dated and undocumented feature.
  • Fixed up Dashboard and Offcanvas examples across Firefox and IE.
  • Breadcrumbs can now use non-string values as dividers.

Be sure to look at the ship list and project board for more details on all our fixes. Also, as a small heads up, we’ve split our issue template on GitHub into two separate templates, one for feature requests and one for bug reports. Please let us know if you have any feedback on the change.

Next release

Next up, we’re looking at a v4.1.1 release. There are some bug fixes for input groups, form fields, and more that I know we need to tackle sooner than later. These were supposed to be in v4.1, but we couldn’t make it happen in time.