In short, Sass has a limitation where once a default variable or map has been used, it cannot be updated. For example, updates to $theme-colors were not being applied to other theme maps that relied on $theme-colors, breaking key customization workflows. It pulls out several Sass maps from _variables.scss to fix an issue where updates to an original map were not applied to secondary maps that extend them. New _maps.scssīootstrap v5.2.0 introduced a new Sass file with _maps.scss. For example, setting $alert-border-width: var(-bs-border-width) in our source code breaks potential Sass in your own code if you were doing $alert-border-width * 2 for some reason.Īs such, wherever possible, we will continue to push towards more CSS variables, but please recognize our implementation may be slightly limited in v5. While we’d love to fully implement these across the board, they do run the risk of causing breaking changes. Our CSS variable usage will be somewhat incomplete until Bootstrap 6. Read more about CSS variables in each component on their respective documentation pages. In subsequent releases, we’ll continue to expand our use of CSS variables into our layout, forms, helpers, and utilities. btn), allowing for more real-time customization of Bootstrap. While Sass still underpins everything, each component has been updated to include CSS variables on the component base classes (e.g. We’ve updated all our components to use CSS variables.
Our documentation also has been updated with a new homepage, simpler docs layout that no longer collapses sections of the sidebar, and more prominent examples of Bootstrap Icons.
Bootstrap v5.2.0 features a subtle design update for a handful of components and properties across the project, most notably through refined border-radius values on buttons and form controls.
0 kommentar(er)
