We’ve updated Bootstrap 4 with a new patch release to fix some bugs, backport some iterative changes from v5, and more. Enjoy!
As you may already know, we’re alternating between v4 and v5 releases to keep both versions moving in tandem. This helps us close the gap between v4 and v5 and make updating to v5 as easy as possible.
Read on for the highlighted changes.
Also available in the v4.5.3 release on GitHub.
- #31653: Add a comment to our
escape-svgfunction to note that data URIs must be quoted.
- #31693: Use the
custom-controlshadow variable instead of the generic
- #31793: Backport some v5 changes (improved
thstyling in Reboot, custom form field styling when printing, and improvements to
- #29714: Keep custom check, radio, and switch theme when printing.
- #30781: Reboot’s
font-weight: boldthat comes from user agent stylesheets.
.text-breakchanges to drop
- #31754: Improve versions page rendering (also reversed the order while I was here)
- #31846: Backports the z-index change to
.closebuttons in dismissible
- #31000: Avoid multiple change event trigger in buttons plugin. Not applicable to v5 since our button JS plugin has been mostly replaced with pure CSS.
- #31673: Fix dropdown variable always evaluating to true.
- #31696: Ensure
hidePrevented.bs.modalcan be prevented.
- #31718: Backports new
$dropdown-padding-xvariable from v5.
- #30811: Mention GPU acceleration fix in docs callout for popovers. Doesn’t apply to v5 since we’re updating to Popper v2.
- #30838: Explain the
disposemethod more appropriately.
- #31706: Backports updated margins for code snippets for improved readability.
- #31769: Backports JS bundle guidance from v5.
- #31851: Backports mention of missing
- #31297: Switch to xo ESLint config
- Updated devDependencies versions
We’ll be back to v5 with our third alpha release coming in a couple of weeks. After that, we’ll ship another v4 update with v4.6.0 that continues the v5 backports and feature development. Please keep the feedback coming on what we can improve, how our releases are performing, and any other suggestions.
Support the team
Visit our Open Collective page or our team members’ GitHub profiles to help support the maintainers contributing to Bootstrap.