Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reactable showing on RStudio but not on Chrome/Safari #363

Open
Lornebradia opened this issue Mar 11, 2024 · 4 comments
Open

Reactable showing on RStudio but not on Chrome/Safari #363

Lornebradia opened this issue Mar 11, 2024 · 4 comments

Comments

@Lornebradia
Copy link

Lornebradia commented Mar 11, 2024

Hi there,

I have a table I'm rendering using Shiny and flexdashboard. The table renders allright in the RStudio preview but it is not on Google Chrome (nor Safari) for reasons I cannot discern.

Using a flexdashboard framework, I have an Rmarkdown file with essentially the following chunk:

renderReactable({
  mtcars |>
    reactable()
})

which is as minimal as it gets. This table will show up in the RStudio Viewer, but it won't show up at all on Chrome. It also doesn't show up in my company's Posit Connect.

Any hints towards why this may be the case would be very appreciated.

on RStudio Viewer on Google Chrome
@igutermes
Copy link

Mine shows a blank screen too... Can't understand why

@igutermes
Copy link

Ok... I tested Firefox, Brave, Chrome and Chromium. Only the later renders reactables.

@Lornebradia
Copy link
Author

I suspect the primary culprit may be flexdashboard, as I am capable of making reactable and Shiny render on Chrome when used directly, but not when using flexdashboard (or Quarto Dashboards) for that matter. It may be an issue with Bootstrap.

@glin
Copy link
Owner

glin commented Mar 30, 2024

It's most likely a JavaScript error that causes the table to go blank, so could you open your browser's developer tools pane, and check if there are any JavaScript errors in red?

I tested this briefly with the latest Chrome on Windows and couldn't reproduce any error. The JS error would help a lot in identifying what sort of conflict this is though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants