You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that {pagedown} does not compile the Paged.js directives (like @page) when included in a Rmd CSS chunk.
Is it by design?
No issues is the CSS is externally included with the css parameter of pagedown::html_paged(), or if the generated Paged.js classes are used in place of all directives (e.g. .pagedjs_page instead of @page).
Not sure if this is by design or not but one important difference is that
When css is used in YAML, it will be added as a node in <head>
When using the CSS engine, the content will be inlined inside the HTML document body using <style>
It is highly possible that paged.js process only the CSS from <link> and not the inline css - or that @page instruction can't work from <style> instruction in <body>
It seems that {pagedown} does not compile the Paged.js directives (like
@page
) when included in a Rmd CSS chunk.Is it by design?
No issues is the CSS is externally included with the
css
parameter ofpagedown::html_paged()
, or if the generated Paged.js classes are used in place of all directives (e.g..pagedjs_page
instead of@page
).Reprex
Using pagedown 0.20, R 4.2.2
The text was updated successfully, but these errors were encountered: