![]() The solution for this is to add the needed space (represented as padding) in an empty header/footer cell to properly separate the content that is split across pages. however the headers/footers replicated in each page don't leave any kind of space by default, this result in having weird layout issues in which header content overlaps rows in other pages. Tables with long content expand across multiple pages as needed, and if you have table headers/footer those will be replicated in each page which the table's content is present. Some users experienced freezing chrome because of wrong indentation of source html, this may sounds strange but it can help to click code reformatĬhrome may do page breaks badly if you use images, it helps if you explicitly set image height in the wrapped div Self closing divs ( ) are heavily slowing down chrome pdf rendering, don't use them Note the same debugging techniques applies also to the chrome-image recipe. To troubleshoot the javascript evaluated in the chrome-pdf recipe, you can write to the console.log and inspect the outputs in the studio profile tab when clicking on the chrome-pdf operation.įor a full chrome-pdf debugging experience, find the video tutorial here. In many cases, you can switch to the html recipe and debug the output using the F12 browser's tool just like any other page. Use chrome-pdf node in the standard config file. The options can be also dynamically set from within the page javascript using. ![]() These basic settings are typically stored with the template, but you can also send them through API calls inside the template.chrome property. The settings reflects the headless chrome API where you can also find detail information. Chrome-pdf recipe is using headless chrome to print html content into pdf files.
0 Comments
Leave a Reply. |