Force Chrome to wait before PDF print about chrome-headless-render-pdf HOT 4 CLOSED

Is this some server side initiated resource? vietual-time-budget simulate all time events (setTimeout etc) to happen up to that time as fast as possible, therefore it will take much less than that time, but it should have the same effect as really waiting that time when all time related logic is happening in browser

from chrome-headless-render-pdf.

The page I'm trying to PDF has some Javascript on it that needs between 1 and 2 seconds to run (which manipulates content in the DOM a bit). Regardless of what I've tried thus far, the rendered PDFs all have only the first couple of ms-worth of that Javascript's work completed. What I'm trying to do is force Chrome to not print for 2000ms.

This may be something in chrome(ium) and not something chrome-headless-render-pdf can do. But I'm not finding a solution other than using something like Puppet directly.

from chrome-headless-render-pdf.

any news on this? I also stuck with the same problem.
Having a page which does call an external REST Api and needs 1-2 seconds to finish.
The screenshot always only contains the progress bar which is shown when page is started.
My code

RenderPDF.generateMultiplePdf(
 [{ url: "https://mywebpage/", pdf: "/tmp/outputPdf.pdf" }],
   {
     chromeBinary: "/usr/bin/chromium",
     chromeOptions: ['--no-sandbox', '--virtual-time-budget','2500']
   })

also tried

RenderPDF.generateMultiplePdf(
 [{ url: "https://mywebpage", pdf: "/tmp/outputPdf.pdf" }],
   {
    chromeBinary: "/usr/bin/chromium",
    chromeOptions: ['--no-sandbox', '--virtual-time-budget=2500']
   })

chrome-headless-render-pdf seems to disrespect this chrome option

from chrome-headless-render-pdf.

U added new option to set increase time budget --js-time-budget from default 5s
from api its jsTimeBudget

from chrome-headless-render-pdf.