Chang W, Cheng J, Allaire J, Sievert C, Schloerke B, Xie Y, Allen J, McPherson J, Dipert A, Borges B (2024). shiny: Web Application Framework for R. -R package version 1.8.0.9000, +R package version 1.8.1, https://github.com/rstudio/shiny, https://shiny.posit.co/.
@Manual{,
title = {shiny: Web Application Framework for R},
author = {Winston Chang and Joe Cheng and JJ Allaire and Carson Sievert and Barret Schloerke and Yihui Xie and Jeff Allen and Jonathan McPherson and Alan Dipert and Barbara Borges},
year = {2024},
- note = {R package version 1.8.0.9000,
+ note = {R package version 1.8.1,
https://github.com/rstudio/shiny},
url = {https://shiny.posit.co/},
}
diff --git a/favicon-16x16.png b/favicon-16x16.png
index da17950a3..c70719ac7 100644
Binary files a/favicon-16x16.png and b/favicon-16x16.png differ
diff --git a/favicon-32x32.png b/favicon-32x32.png
index 41e41ba23..65b89937c 100644
Binary files a/favicon-32x32.png and b/favicon-32x32.png differ
diff --git a/index.html b/index.html
index 4f5865210..97ecf242a 100644
--- a/index.html
+++ b/index.html
@@ -43,7 +43,7 @@
diff --git a/news/index.html b/news/index.html
index 95e09c0ae..4dd9dab1f 100644
--- a/news/index.html
+++ b/news/index.html
@@ -17,7 +17,7 @@
@@ -48,22 +48,22 @@
renderDataTable()/dataTableOutput() are officially deprecated in favor of their {DT} equivalents, renderDT()/DTOutput(). In most cases, simply changing renderDataTable() to DT::renderDT() and dataTableOutput() to DT::DTOutput() is sufficient for upgrading. Also, to promote migration, when a recent version of DT is available, renderDataTable()/dataTableOutput() now automatically use their DT equivalent (and provide a message that they are doing so). If this happens to degrade an existing app, set options(shiny.legacy.datatable = TRUE) to get the old (i.e., non-DT) implementation. (#3998)
Both conditionalPanel() and uiOutput() are now styled with display: contents by default in Shiny apps that use Bootstrap 5. This means that the elements they contain are positioned as if they were direct children of the parent container holding the conditionalPanel() or uiOutput(). This is probably what most users intend when they use these functions, but it may break apps that applied styles directly to the container elements created by these two functions. In that case, you may include CSS rules to set display: block for the .shiny-panel-conditional or .shiny-html-output classes. (#3957, #3960)
The examples behind runExample() now use bslib to generate a better looking result. To instead run the “legacy” examples, set options(shiny.legacy.examples = TRUE) before calling runExample(). (#3963)
Added an console that shows some errors in the browser. Also provide better error messages for duplicate input and output bindings. (#3931)
Added a new ExtendedTask abstraction, for long-running asynchronous tasks that you don’t want to block the rest of the app, or even the rest of the session. Designed to be used with new bslib::input_task_button() and bslib::bind_task_button() functions that help give user feedback and prevent extra button clicks. (#3958)
Added onUnhandledError() to register a function that will be called when an unhandled error occurs in a Shiny app. Note that this handler doesn’t stop the error or prevent the session from closing, but it can be used to log the error or to clean up session-specific resources. (thanks @JohnCoene, #3993)
runExamples() now uses the bslib package to build the user interface (UI). It also gains a package argument so that other packages can leverage this same function to run Shiny app examples. For more, see ?runExamples. (#3963, #4005)
Notifications are now constrained to the width of the viewport for window widths smaller the default notification panel size. (#3949)
Fixed #2392: downloadButton() now visibly returns its HTML tag so that it renders correctly in R Markdown and Quarto output. (Thanks to @fennovj, #2672)
Calling updateSelectizeInput() with choices and selected now clears the current selection before updating the choices and selected value. (#3967)