If you are printing things like documentations, maybe amending to the concept of a print page is not a bad idea.
await page.emulateMediaType('screen') You are going to end up with a single huge chunk of PDF in some cases, similar to what a user would have done trying to print that page using Chrome. Nevertheless, if your code is indicating the headless browser to behave as screen e.g. What you saw there, is what you will be getting. In a nutshell, you know when your print is ready when you can simply do this in Chrome as a user: In other words, if a website was already printing in multiple pages for a given document, Puppeteer follows along and will do the same thing. The idea of creating multiple pages has to do with CSS paged media.
You can add all the content of your web app in one page or have Puppeteer looping through a list of pages. You have hidden code for this example, therefore I cannot tell what is happening 100%.
0 kommentar(er)
