bs_theme() now defaults to version = 5
(i.e., Bootstrap 5). If this change happens to break an existing app,
consider specifying bs_theme(version = 4) to revert the
change in the Bootstrap version. (#374).navbar-default/.navbar-inverse class has
changed slightly to better match their Bootswatch 3 coloring. Also,
since this coloring is now based solely on $navbar-*
variables, Bootswatch themes now work better in combination with
custom $navbar-* values (e.g.,
bs_theme("navbar-bg" = ...) can be used to provide the
background color, and foreground colors will automatically contrast
appropriately). (#392)bs_theme(version = 5)) from
5.1.0 to 5.1.3 (#378)bs_dependency_defer() now memoises
func (by default), reducing the time required to render
multiple instances of the same dynamically
themable widget. (#405)$form-check-label-*
variables now work as expected with shiny::radioButtons(),
shiny::checkboxInput(), and
shiny::checkboxGroupInput(). (#395)shiny::checkboxInput(),
shiny::checkboxGroupInput(), and
shiny::radioButton() with
bs_theme(version = 5, bootswatch = "sketchy"). (#385)shiny::tabsetPanel(type = "hidden") (i.e.,
bslib::navs_hidden()) stays hidden when used with
bs_theme(). (#379)nav_menu() appearing
first in a navs_*() container with Bootstrap 4+.nav_menu(align="right") now works with
Bootstrap 5. (#401)bs_theme(bootswatch = "paper", version = 5) or
bs_theme(bootswatch = "readable", version = 5) no longer
errors. (#391)bs_theme(version = 5)) from
5.0.2 to 5.1.0 (#365)nav_menu() (i.e.,
shiny::navbarMenu()) wasn’t producing an
.active class on it’s .dropdown container
properly. (#372){magrittr}’s pipe
operator (%>%) is no longer re-exported by
{bslib}. Either library(magrittr) to make
%>% available and/or use use R 4.1’s pipe operator
(|>).bs_theme(version = 5)). Bootstrap 4 remains the default in
this release, but the next release, the default will likely change to
Bootstrap 5.Small patch release to fix failing test on Solaris.
bs_theme() options
(navbar-bg, navbar-light-bg, and
navbar-dark-bg) for more easily customizing the navbar’s
background (and foreground) color (#253, #271).bs_theme() argument
(font_scale) for easier scaling of the base font size
(#288).font_google(), font_link(), and
font_face()) are now re-exported from the
{sass} package. As a result, they may now be used with any
Sass variable (e.g.,
bs_theme("input-font-family" = font_google("Pacifico"))) as
well as inside Rmd yaml without !expr (e.g.,
input-font-family: google: Pacifico – see #256 for more
details). A new font_collection() function was also added
for a more convenient way to specify font fallbacks (#291).bs_themer() now emits sensible
yaml front matter when used within an Rmd document
(#288).bs_themer() now overlays a spinner during
Sass compilation (#243).{bslib} now includes
rmarkdown::html_document templates demonstrating example
usage with {bslib} and {thematic} (#288).<blockquote> tags now have
border-left/padding styles with version = 4 (to mirror the
version = 3 behavior) (#239).shiny::devmode() is enabled. To
enable/disable these warnings, set the new
options(bslib.color_contrast_warnings = ) to
TRUE/FALSE (#287).bs_theme_dependencies() now includes Sass source maps
when shiny::devmode() is enabled (#312).bs_add_functions()/bs_add_mixins() and
deprecated bs_add_declarations() to reflect
sass::sass_layer()’s new ability to place
functions before variable defaults.
As a result, variable definitions may now use functions defined with
bs_add_functions(). (#311)