mirror of
https://github.com/rstudio/shiny.git
synced 2026-01-29 00:38:19 -05:00
If reactivePrint or reactiveText return non-ASCII characters on Windows, it causes invalid UTF-8 strings to be received by the browser which closes the websocket connection. I'm not sure this is the right place to do encoding, but it seems to me like this approach is likely to work best for the most users (especially those who just aren't thinking about encoding). If you want to handle encoding in the reactives themselves (for example), use `options(shiny.transcode.json=F)`.