-
Notifications
You must be signed in to change notification settings - Fork 24
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
HTML widgets that don't work in the Academic theme #36
Comments
I suspect these are mostly going to be css/js clashes and hence (currently) outside the scope of hugodown, but it's worth documenting them listing known work arounds. |
|
The issue with plotly seems to be related to its propensity to meddle in the MathJax config. I got it to work by adding this line before the <script>window.PlotlyConfig = {MathJaxConfig: 'local'}</script> Reference: https://github.com/plotly/plotly.js/blob/master/dist/README.md#to-support-mathjax |
I'll add to the list of HTML widgets that need workarounds. I can't get @hadley, would you be interested in starting a wiki page for the community to track problematic widgets and their workarounds? |
@apreshill: First, the post's preview text looks like this: Second, the Reactable doesn't display well in dark mode: I tried to make this process minimal. I did this on a fresh R 4.1.0 installation on Windows 10 in RStudio 1.4.1717:
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = FALSE, message = FALSE, warning = FALSE)
```
Lorem ispum.
```{r}
reactable::reactable(iris)
```
|
Hi-
Using
create_site_academic()
, a few HTML widgets don't work out of the box:plotly (I'm unable to debug this, it isn't just a jquery clash)
highcharter (this works if I add a page parameter to disable Academic's jquery version, but then for some reason the post title is partially hidden by the upper navbar 🤷♀️ )
DT::datatable (this only works if I add a page parameter to disable Academic's jquery version; does not appear to affect CSS)
reactable does work, even without any page parameter.
I'll test out a few more, but wanted to start an issue to track this.
The text was updated successfully, but these errors were encountered: