If you set a specific paper size and the content that you are trying to export to PDF exceeds the size of the paper, the content is cut off. The RadClientExportManager needs to overflow this content to a new page. This functionality would be consistent with the RadGrid's PDF export capabilities. Without it, the RadClientExportManager is only useful for generating PDFs IF one knows the exact size/dimensions of the content being exported.
Could you also add in as part of this the ability to respect the page's auto-width. For instance when you have a web page that is coded for a width of 100% and a page size is selected, the percentage is not respected and as a result the page would auto roll to another page even though the webpage was configured to dynamically size to the display media. For example. If you printed the page using percentages instead of pixels it will autosize correctly when printed on a printer, but it doesn't render properly when rendered by radclientexportmanager.
Thank you for pointing out this valid scenario. I've changed the status to approved.
Rumen Jekov, please return this item to the status of review. The issue at hand is when you have content of a dynamic size, for instance a data repeater, you cannot just toss in a pagebreakselector and be good. The radclientexportmanager should be able to know that the content being exported exceeds the page size and automatically insert a new page.
The following demo shows how to export multi-page content - https://demos.telerik.com/aspnet-ajax/client-export-manager/functionality/pdf-multi-page-export/defaultcs.aspx