You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In titlePanel, the windowTitle argument defaults to title. If the title is complicated, this can end up with arbitrary HTML, CSS, and script tags being inserted into the head, which can break shinyapps.io, Connect, and Shiny Server when they go to inject their SockJS scripts:
One possibility discussed with @aronatkins would be to only take the title as the default value if it's a string, or alternatively, walk the first level of the tree looking for strings (which would let you at least put a logo). We could emit a warning if the title is too complicated to extract a windowTitle, asking the user to provide one explicitly.
The text was updated successfully, but these errors were encountered:
* Use bslib's new nav() api to implement tabPanel() and friends
* bslib won't be re-exporting prepend/append tab since they've been superceded by insertTab()
* Update DESCRIPTION
* Use the new bslib::page_navbar()
* Leverage bslib::page_navbar()'s more intelligent title->windowTitle handling
Closes#2310
* fix name change
* Make sure navbarPage() isn't browsable by default
In
titlePanel
, thewindowTitle
argument defaults totitle
. If the title is complicated, this can end up with arbitrary HTML, CSS, and script tags being inserted into the head, which can break shinyapps.io, Connect, and Shiny Server when they go to inject their SockJS scripts:One possibility discussed with @aronatkins would be to only take the
title
as the default value if it's a string, or alternatively, walk the first level of the tree looking for strings (which would let you at least put a logo). We could emit a warning if thetitle
is too complicated to extract awindowTitle
, asking the user to provide one explicitly.The text was updated successfully, but these errors were encountered: