When printing a document with multiple pages, the pages that are not currently visible will be printed without content.

There is opportunity to further optimize the caching mechanism of the image sources, which will reduce the memory consumption. The fast scrolling in a document containing big images could lead to an OutOfMemoryException.

Available in R1 2017 Official Release Version.

If the presenter is changed (for example, by pressing "Fit one full page to window" button) during the inertia of a scroll operation, NullRererenceException is thrown.

Fix available in LIB Version 2017.2.627.

With the current implementation, it takes seconds to decode and display JPEG with several megapixels (for example size 4000 x 2000 pixels). The memory consumption when decoding such images also needs improvements.

Workaround: Custom DctDecode filter may be implemented and registered in RadPdfViewer. The attached demo shows how this may be achieved by using BitmapImage class to decode the JPEG images instead of the default RadPdfViewer's JpegDecoder.

All annotations are missing because ArgumentNullException is thrown while importing page annotations. The exception is handled and all non-annotation related pdf content is loaded successfully.

Printing document on a machine with .NET Framework 4.6 installed does not work for some documents.

Currently, an issue is opened at Microsoft Connect: "Printing with PrintDialog fails when .NET 4.6 is installed" (https://connect.microsoft.com/VisualStudio/feedback/details/1980419/printing-with-printdialog-fails-when-net-4-6-is-installed).

Workaround: In the attached project.

This usually results in a single colored rectangle instead of a gradient filled rectangle.

Available in R1 2018 SP2 release version.

Currently, we have reproduced this issue with fonts AmnestyTradeGothic, OfficinaSanITC and OfficinaSanITC-Book.

The fix will be available in our official release 2015 Q2. 

When having Pdf with SimpleFont that does uses glyphs with missing width their width is calculated as zero due to wrong integer calculations.

The issue is reproducible only for some specific font files. The characters are displayed as rectangles. This seems to caused by incorrect glyph name and glyph id mapping.

The fix will be available in our official release Q2 2015 SP.

The fix will be available in our next LIB release (v. 2015.02.0706).

Available in R2 2017 Release

The fix will be available in our official release Q2 2016.

When a PDF document contains images compressed with CCITTFaxDecode with applied BlackIs1 parameter, black color is visualized as white and white as black.

The feature  will be available in our official release 2015 Q2.