Closed
Description
The chrome_print
function is great! Thanks!
When I use chrome headless on html pages with paged.js, I always need the --virtual-time-budget
CLI argument. It seems to be logical because paged.js is launched when the page is loaded. If I understand well chrome headless, the pdf is built at the same time. So, the DOM is not processed by paged.js before the pdf generation.
On average documents (paged.js+mathjax stuff, 30 pages), I often need to allow a budget of 5 to 10e+06 virtual milliseconds (5-6 effective seconds).
BTW, with puppeteer, it is easier to control that paged.js has finished its job.
What do you think of adding an argument to chrome_print()
for the virtual time budget?
Metadata
Metadata
Assignees
Labels
No labels