Problem with reactable table when knitting with chrome_print

[maibennett]

Hi,

I had an issue when trying to knit a reactable table using chrome_print. For some reason, when I don't include LaTeX code, the reactable table doesn't show up in the PDF, but if I do, then it actually shows up.

Here's a simple reproducible code, if it's useful:

1. This is the code that works:

---
title: "Example for reactable"
author: "maibennett"
date: "April 14th, 2021"
output:
  pagedown::html_paged:
    toc: no
    number_sections: no
paged-footnotes: true 
knit: pagedown::chrome_print
---

```{r setup, warning=FALSE, message=FALSE, echo=FALSE}
library(tidyverse)
library(reactable)
library(htmltools)
```

$$\text{Including this, works}$$

```{r, echo = FALSE, message=FALSE, warning=FALSE}

data(USArrests)
   
USArrests_s <- USArrests %>% dplyr::filter(rownames(.)=="Alabama" | rownames(.)=="Alaska")

tbl <- USArrests_s %>%
  reactable(
    pagination = TRUE,
    rownames = FALSE,
    defaultColDef = colDef(
      align = "center",
      minWidth = 90)
    
  )

div(
    class = "title",
    h3("This is a table"),
  tbl
)

```

2. This code doesn't show the reactable table:

---
title: "Example for reactable"
author: "maibennett"
date: "April 14th, 2021"
output:
  pagedown::html_paged:
    toc: no
    number_sections: no
paged-footnotes: true 
knit: pagedown::chrome_print
---

```{r setup, warning=FALSE, message=FALSE, echo=FALSE}
library(tidyverse)
library(reactable)
library(htmltools)
```

```{r, echo = FALSE, message=FALSE, warning=FALSE}

data(USArrests)
   
USArrests_s <- USArrests %>% dplyr::filter(rownames(.)=="Alabama" | rownames(.)=="Alaska")

tbl <- USArrests_s %>%
  reactable(
    pagination = TRUE,
    rownames = FALSE,
    defaultColDef = colDef(
      align = "center",
      minWidth = 90)
    
  )

div(
    class = "title",
    h3("This is a table"),
  tbl
)
```

I've included both PDFs outputs. If anyone has an idea of why this might be, I'd really appreciate it! Thanks.
reactable_example2.pdf
reactable_example1.pdf

[RLesur]

Hi @maibennett,

Thanks for the report!

The reactable package is not yet supported by html_paged() as any other HTML widget (see #58) but we have a candidate solution (see #87) that we will merge soon.

There are many challenges to solve with HTML widgets. One of them is the synchronization between the HTML widgets and Paged.js (Paged.js must run after the widgets are rendered). We have the same synchronisation puzzle to solve for any JavaScript library.
For instance, pagedown synchronizes well MathJax and Paged.js: equations are rendered before Paged.js starts.

Your working example is really interesting because using maths, it indirectly synchronizes the HTML widget with Paged.js (the widget is rendered before MathJax and Paged.js waits for MathJax): this is an undocumented positive side effect 😄

[maibennett]

Thanks! It's great to know at least why this happened 😄 (and thanks for all the work in this great package!)