This might result in invisible annotations.

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

FixedDocumentPresenter could be TemplateBound to PDFViewer's Background property.

Available in LIB version: 2016.3.1205

The instances are kept in GeometryRenderer cache and each time the content stream is parsed new PathGeometry instances are added to GeometyRenderer store Dictionary field.

Available in R1 2017 Official Release Version.

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

Available in R1 2018 SP2 release version.

"Save As" is common functionality in most of the popular PDF Viewers. It should save the currently loaded document to a file.

Workaround: Currently there is SDK demonstrating how to add such functionality: https://github.com/telerik/xaml-sdk/tree/master/PdfViewer/PdfViewerCustomSaveCommand

Available in R3 2017 Official Release Version.

Parsing the wrong content stream in RadPdfViewer results in handled exception and this way some of the PDF content is missing when rendering the page.

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.

The visualizations of all annotations are defined by their normal appearance streams. This is already implemented in RadPdfViewer for the supported annotation types (Link and Widget annotations). It may be easily adopted for not supported annotation types as well.

Available in 2017 R3 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.

Please implement Crypt Filter for PDFs to open RC4 (40Bit, 128Bit) and AES (128Bit,256Bit) pdf Files inside PDFViewer.

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.

Currently, all images are decoded and preserved in RGBA format (32 bits for each pixel). However, there are files that optimize their images by preserving them with 1 bit for each pixel. In WPF we may create monochrome System.Windows.Media.ImageSource that would optimize the performance and memory consumption when rendering such images.

Available in R1 2018 Official Release Version.

When this feature is implemented it should visualize the bookmarks similarly to in the attached screenshot.

Available in R3 2018 Official Release Version.

Available in R2 2017 Release

Import documents that use this type of encryption. Currently, a handled NotSupportedEncryptionException is thrown while importing such a document and it cannot be opened in RadPdfViewer.

Available in R1 2018 Official Release version.

Customers are reporting an issue when trying to copy content in an application hosted on a remote machine (there are reports using TigerVNC and Citrix).  The exception is thrown from the Clipboard class with a message: OpenClipboard failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN)).

It seems like such a behavior could be reproduced when the clipboard is already opened by another application. Here is a discussion on the matter: https://stackoverflow.com/questions/68666/clipbrd-e-cant-open-error-when-setting-the-clipboard-from-net

Fix available in LIB Version 2018.3.1029.

When importing documents containing Interactive FormFields with an empty collection of Normal state appearances, a NullReferenceException is thrown, which leads to non-editable FormFields in PdfViewer.

Fix available in LIB Version 2018.2.730.

Instead, we should not visualize them and they should not be interactable with the mouse.

Fix available in LIB Version 2018.2.730.

RadPdfViewer's AcroForm property ViewersShouldRecalculateWidgetAppearances should be respected when being set to true. In this case, RadPdfViewer should recalculate all widget appearances and this would resolve the issue with empty form field widgets after opening such PDF document.