HTML Widgets not displaying about blogdown HOT 9 CLOSED

I just got around to trying this, and you're totally right. Using htmlwidgets::saveWidget(figure, file = "figure.html", selfcontained = TRUE) to output the widget and then adding each file as an iframe within the .md file of the project works like a charm!

It is worth noting (for others with this issue), that Hugo will rename the html file when transferring it to the public folder. So, if you had a figure in this location: "figures/fig.html", your iframe should actually read <iframe src="figures/fig/index.html></iframe> in the .md file when working with Hugo.

from blogdown.

I've had some issues with CSS conflicts between htmlwidgets and various Hugo themes. I'm not 100% sure but this may be something that would have to be resolved theme by theme.

A good workaround is to use htmlwidgets::saveWidget() to save your chart to an HTML file then embed in your blog as an iframe. @bhaskarvk is also working on a solution for this with his widgetframe package (https://github.com/bhaskarvk/widgetframe)

from blogdown.

I'm working on automating this step via https://github.com/bhaskarvk/widgetframe. But there are some issues that I still need to resolve. Stay tuned.

from blogdown.

Don't use the amazing widgetframe package, as it's abandonware and had a security vulnerability since 2018.

from blogdown.

Great, I'll look into those options. Thanks!

from blogdown.

Hi all, I am experiencing similar issues with highcharter, wordcloud2 and (sometimes?) plotly. I tried to use @bhaskarvk 's widgetframe::frameWidget() but it deos not solve the issue. I am using the hugo-academic theme btw.

Is there any progress in this issue or anyone experienced similar things?

from blogdown.

I had similar issues with highcharts charts not rendering on a recent blogdown post, and after trying a few solutions I solved it in a bit of a workaround that potentially could be more automated, here is how I approached it:

1. within an R chunk create a highchart htmlwidget object, say hc as one normally would
2. export the object using highcharter::export_hc(hc, "filename.js")
3. use htmltools::includeHTML("filename.js") to inject the js into the page source, wrap it between <script> tag and place it in a <div> like so:

<script type="text/javascript">
# included js from filename.js here 
</script>
<div id="container"></div>

This can get tedious if you want more than 1 chart on a page as export_hc automatically calls it container -> one may spend some time to add a bit more flexibility to the function in terms of the export if this proves useful.

Note that you of course need the javascript resources provided on the page, for example using something like

htmltools::includeHTML("include_highcharts.html")

where that include_highcharts.html contains the needed links, such as (or more likely your "local" copy of those):

<script type="text/javascript" src="https://code.highcharts.com/highcharts-more.js"></script>

from blogdown.

Just use the amazing widgetframe package.

from blogdown.

I had the same issue with the Hugo Apero theme where echarts4r canvas elements were shown as blank. For me the widgetframe package did not work. The only option that did work was to render the graph in a separate R file and save it using the htmlwidgets::saveWidget() function and then include the html file in the blogdown file using the includeHTML() function

from blogdown.