I also have similar problems. In my case, I have a container as a target of my downloadPage in which its vertical length is dynamic due to table items it has inside. Once the container is pretty long, the utils.downloadPage() result is chopped to certain length.
Is there any other secondary parameter that I need to set in order to make it work?
As an additional information. I have a custom css applied to this a component (viewClientBBP--0 is the newest table component)
#viewClientBBP--0 {
max-height: none;
}
This CSS is meant to show the table in fixed height. If this custom CSS script is not there, somehow the height of the table will become fixed once it reaches certain height.
Not sure whether this cause the downloadPage functionality to be cropped once it reaches certain height.
Thanks for reporting this @Christoforus_Widodo. Seems like a few users have reported this as an issue. I've logged this bug and will respond here with any updates.
Unfortunately no update yet. But I have personally gathered several tickets related to utils.downloadPage and .serializePage to get some engineering attention on either switching the JS library used under the hood or developing our own tooling to make it easier for users to export PDFs of their apps.
Will update this thread with any news that I get from the eng team on what our roadmap will be for improving the util methods as we want to get this fixed to support the needs of our users.