New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PagedJS - Chrome Headless - Partial Rendering Problem #183
Comments
hi there. you can check how it’s done on pagedjs-cli repo (or simply it :D) https://gitlab.coko.foundation/pagedjs/pagedjs-cli/ tell us if that helps. |
Thank you but the environment is not at my control, there are only chrome
and firefox.
…On Mon, Feb 19, 2024, 17:46 julientaq ***@***.***> wrote:
hi there.
you can check how it’s done on pagedjs-cli repo (or simply it :D)
https://gitlab.coko.foundation/pagedjs/pagedjs-cli/
—
Reply to this email directly, view it on GitHub
<#183 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKZMAUPZZMF7YPZ3YQ6OEEDYUNQV7AVCNFSM6AAAAABDPSTNAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSGYYDCNJQGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
i’m curious how do you use chrome headless? without pupeteer? in any case, do you have the right content when you’re not headless? do you have some code for us to try? |
example.zip Running this command It works if I set virtual-time-budget like 2147483647 (which is literally the max value it can take, it also works close values like 1000000000), but that is a quite bad solution and still doesn't guarantee. I presume the underlying reason is async functions of paged.js |
Take a look at the Drupal module printable, which I also maintain. I've got a file named waitFor.js (from memory) in there, that provides different ways of waiting for pagedJS to do its work. It might be helpful. |
When using paged.js with google chrome headless in order to print pdf, it goes to the stage of printing as pdf before paged.js has able to finish its work.
Any way to overcome this ?
The text was updated successfully, but these errors were encountered: