Multi-page PDFs cause page errors in Adobe Reader, when created with .html()

[r3-gabriel]

I have read and understood the contribution guidelines.

When creating a PDF document via .html() with autoPaging enabled, Adobe Reader reports errors from the second page onward (jsPDF 2.5.1 / html2canvas 1.4.1).

The issue does not occur in PDF viewers in Chrome or Firefox. I´ve created a CodePen that reproduces this issue.

I also found a workaround: If I know the number of pages that the autoPaging will generate with .html(), I add those pages manually beforehand - this will result in a PDF file that works in Adobe Reader without issue. CodePen with workaround.

Because of this, I assume that autoPaging in .html() does not properly manage pages, which triggers the error.

[JasmeenTechnocomet]

I had the same problem @r3-gabriel did you find any solution?

[r3-gabriel]

I have not had more time to investigate - the descriped workaround worked good enough to address the issue in the short term.

To clarify how the workaround is implemented:

• Create PDF normally with .html(), which results in the bug in Adobe Reader
• Count the resulting pages
• Throw away the created document
• Create new, empty PDF
• Add the expected number of pages manually with .addPage()
• Add content with .html()
• Now you have a valid PDF document

Because the workaround fixes the issue, I assume that .html() does not register pages correctly when more than 1 is generated.

[riquems]

Same problem here, thanks for the workaround @r3-gabriel. Hope this gets fixed...

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

[r3-gabriel]

Bump, still relevant.

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

[r3-gabriel]

Bump, still relevant.

[ruanpetersen]

I am also rendering a multi-page PDF and am also experiencing this issue but due to images. When images are removed then the error goes away. I have tried multiple image formats.

[hansdoug]

@r3-gabriel wow, thank you for the workaround, you just saved my day.

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.