FixedDocumentPresenter could be TemplateBound to PDFViewer's Background property.

Available in LIB version: 2016.3.1205

The exception is thrown while decoding TIFF images. Although the document is properly loaded and the end user is not impacted, the DivideByZeroException is logged and present in the OnException event handler parameters. 

The PdfViewer won't load a document from PdfDocumentSource created from Uri and the ReadOnDemand option.
Here is an example: new PdfDocumentSource(new Uri("webaddress/somefile.pdf"), FormatProviderSettings.ReadOnDemand);

Available in LIB Version 2017.1.130

Decode array for image masks with DeviceGray color space is not respected, and always the default array of [0 1] is used for visualization. When the mask is encoded with [1 0], the mask is applied inversed, making the wrong pixels transparent. This may lead to images becoming invisible.

Fix available in LIB Version 2017.3.1120.

The current implementation relies on the graphic state color to be always SolidColorBrush. However, it may be other color type and InvalidCastException is thrown. This results in missing content.

Available in LIB version 2017.1.410.

NullReferenceException is thrown when importing a document with AcroForm referencing a missing object for fields collection. This is a regression as the same document will be imported without a problem in previous versions of RadPdfViewer as the AcroForm object would be entirely skipped.

When annotations have annotation flag Print they should be visualized when printing the document. Usually, Widget annotations have such flag and currently RadPdfViewer does not print them at all.

Available in LIB Version 2017.3.918.

This may result in seeing the pattern as a solid color or even not seeing it at all if this color is white and coincides with the background of the page.

The UserDict collection is not parsed and the procedures for the operators are unavailable. The exception is thrown while trying to read the font file of the Univers and Univers Bold fonts.

Internally, an ArgumenNullException is thrown, which results in missing content when the document is shown in RadPdfViewer.

The appearance of such invisible annotation is not imported property and the viewer is trying to recalculate it in an infinite recursion which causes the StackOverflowException.

Fix available in LIB Version 2017.3.1009.

Currently, the implementation relies on the fact that the previous cross-reference value of a stream object is always a stream object. Instead during the cross-reference recursion, we should check on each step whether the previous cross-reference item is table or stream.

Fix available in LIB Version 2017.3.1120.

This may result in inversed transparency issue when rendering images with ImageMask.

Fix available in LIB Version 2017.3.1120.

For some fonts the issue is present. Some of them are:

KozGoPro-Medium

KozMinPro-Regular

KozGoPro-Bold

Setting Handle property to false should result in rethrowing the exception and interrupting current RadFixedDocument rendering. This is related to Exception Handling Mechanism mentioned in this documentation article: 

https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/document-model/exceptionhandling

This exception seems to be caused because the stream is not decrypted correctly and the stream data is corrupted. For instance when the stream is with FlateDecode filter the exception is InvalidDataException with message "Unknown compression method".

At the moment the theme of the RadPdfViewerToolBar can be set only by setting the theme of the entire application. The individual setting (using telerik:StyleManager.Theme="Windows8") should also be supported.

This is not a valid PDF scenario as having appearance state requires having multistate appearances. However, we should handle this invalid document scenario on our side so that the app does not crash with NullReferenceException.

This is reproducible when the field VariableTextProperties has zero value for font size. 

Fix available in LIB Version 2018.1.402.

Currently, RadPdfViewer uses default constant value for the font size in this scenario.

An ArgumentException is thrown internally as the font name is null. However, the name is defined in the base font and can be obtained from it.

Fix available in LIB Version 2018.1.402.