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
Paged.js takes into account only the first @page {...} statement it finds.
So, if the user wants to overrule the @page statement using a custom.css file, it is:
possible with html_paged(css = c('custom.css', 'default-page')
impossible with html_paged(css = c('default-page', 'custom.css')
This is a low priority bug but I'm unsatisfied by this behavior that violates the CSS precedence property.
I see two ways to modify this behavior:
isolate the @page statement in a specific CSS file that could be removed by the user.
include the @page statement in the pandoc template and create variables for paper size and margins (maybe the same as in the pandoc's default LaTeX template).
We also can wait for the bugfix in Paged.js.
The text was updated successfully, but these errors were encountered:
Paged.js takes into account only the first
@page {...}
statement it finds.So, if the user wants to overrule the
@page
statement using acustom.css
file, it is:html_paged(css = c('custom.css', 'default-page')
html_paged(css = c('default-page', 'custom.css')
This is a low priority bug but I'm unsatisfied by this behavior that violates the CSS precedence property.
I see two ways to modify this behavior:
@page
statement in a specific CSS file that could be removed by the user.@page
statement in the pandoc template and create variables for paper size and margins (maybe the same as in the pandoc's default LaTeX template).We also can wait for the bugfix in Paged.js.
The text was updated successfully, but these errors were encountered: