The RadClientExportManager control's known limitations are listed below:
no support for RTL text
no rendering of shadow DOM
no CSS box-shadow, text-shadow, radial gradients (linear gradients are supported).
only solid border-style
using browser zoom other than 100% is not supported.
the content of the following elements is not rendered:
<canvas>will be rendered as an image, but only if it's "non-tainted" (does not display images from another domain).
SVG referenced with the
<img>tag will not render in Internet Explorer, because IE taints the canvas.
<select>elements is imperfect (some minor issues can be noticed, like wrong padding or missing the dropdown arrow).
images hosted on different domains might not be rendered, unless permissive Cross-Origin HTTP headers are provided by the server. Similarly, fonts might not be possible to load cross-domain. Even with the proper CORS headers, IE9 will not be able to load images or fonts from another domain, and could raise a uncatcheable security exception. If you need to support IE9, make sure to host images and fonts on the same domain as the application.
images will not be exported in IE if their source is an SVG document. These are considered to be tainted.
the border-collapse:collapse style of tables is not supported. Avoid using adjacent borders for separate table cells to prevent double borders in the PDF output.
maximum document size is limited to 5080x5080mm (200x200 inches) by the PDF 1.5 specification. Larger files might not open in some viewers.
when the generated document is opened with Acrobat Reader and you try to use the Save As option from the file menu an error is thrown. "The document could not be saved. There was a problem reading(23)". The solution is to open Acrobat Reader options (Edit → Preferences) and in the "Documents" section uncheck “Save As optimizes for Fast Web View”, which is enabled by default. After this, Save As will work without errors.
exporting images from another domain requires the server to have the following header in its response: Access-Control-Allow-Origin:
*, which will enable cross-origin requests. If the server does not have this header set access to the image will be denied and it will not be exported.
exporting font icons
exporting pseudo:elements borders (for example RadOrgChart connection lines)
exporting RadHtmlChart controls with page breaks
This is caused by a bug in the underlying Kendo Drawing API that is fixed in the R1 2017 SP1 release of Kendo, but this version is not yet available in the UI For ASP.NET AJAX suite.
A workaround is to fetch the newer Kendo scripts and perform the export directly with them: MultiPage Export with Kendo Drawing API.
If you take this approach, migrate your charts to Kendo charts as well, in order to avoid mixing the Kendo scripts you will put on the page with Kendo scripts RadHtmlChart will bring. RadDiagram, RadGauge, RadGantt, RadTreeMap, RadMap, RadSpreadsheet, RadClientExportManager and RadClientDataSource are also wrappers over Kendo widgets, so if you use them on the same page where you will include the newer Kendo version, you need to migrate them to their Kendo counterparts as well.