Open andrewheiss opened 6 months ago
The short gist: This isn't likely to happen anytime soon.
The longer gist:
I think some extra markup is happening with the rmarkdown::print.page_df()
and knitr::asis_output()
functions that assumes rendering from a static source.
Other hiccups relate to the meta
dependencies being unable to be added to the document as we're past the render stage. Though, I think the dependencies themselves assume that the document is opened with the data embedded as the output from rmarkdown::paged_html_table()
consists of a div
with a script
tag containing dumped data.
On {quarto-webr}
's end, we'd need the results: asis
mode to avoid marking up content instead of only allowing it to pass through. c.f. #166
Ok cool cool, I'll just live with the default data.frame and tibble-based print()s. In my actual use case, I ended up showing the data frame that learners are working with using a separate, normal {r}
chunk with a paged data frame, so they can still navigate the larger dataset.
Feature Description
In {learnr}, the results from printing data.frame output are shown as paged tables by default (using
rmarkdown::paged_table()
, I think)I've tried to recreate something similar with {quarto-webr}, but something along the way isn't working, and I'm not sure what.