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

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. 

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 is not quite a valid PDF file scenario according to PDF file specification. However, we may try handling it in order to show the correct number of pages. When the kid is of type Pages, it should be added to the pages traversal recursion only the first time it is met.

Default RadPdfViewer presenters load image sources async which allows to render the rest PDF content faster. However, FixedDocumentSinglePagePresenter loads images syncrhonously and all page content is rendered right after all images on the page are loaded.

Setting DocumentSource throws NullReferenceException when PdfViewer is hosted in ElementHost. When setting the DocumentSource, the Application.Dispatcher is used, but in Winforms app, the Application is not instantiated. 

Steps to reproduce:
1. Host PdfViewer in ElementHost in a WinForms application
2. Set the DocumentSource property
3. Run
Expected: The document is opened
Actual: NullReferenceException is thrown

Workaround: the document could be set to the Document property of PdfViewer. Or instead hosting the PdfViewer for WPF in ElementHost, use WinForms version of the control.

Tint transformation function is used to transform Device N color in Alternate colorspace.

By using "Auto Detect Hyperlink" functionality RadPdfViewer should detect URLs and email addresses and turn them into hyperlinks. For instance if the PDF file contains text http://www.telerik.com/ this text should become a hyperlink.

Represents Free text PDF content.

Since LIB Version 2017.3.925 annotations of type FreeText can be visualized.

There is a similar question in FAQ for FontForge (https://fontforge.github.io/faq.html#mingliu) where it is described that kaiu.ttf (and probably mingliu.ttf) font does not store the correct outlines and its outlines need special treatment in order to be rendered correctly. The Chinese glyphs are rendered wrong in RadPdfViewer as well. However, Adobe Reader, FoxitReader and ChromeViewer render the glyphs correctly.

Currently, the disabling of the scrolling functionalities in PdfViewer is pretty tricky. Expose an API that allows users to control this functionality easier (hiding the scroll bars, disabling horizontal and/or vertical scrolling).

A sample of how the scrolling could be completely disabled is attached to this item.

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

Available in R1 2018 SP2 release version.

The ActionsManager.ExecuteUri method throws exception when tries to open relative Uri. As the exception is caught, with the current state no action is observed when interacting with such link in RadPdfViewer.

GoToPage() method is not working correctly in some cases when called in DocumentChanged event handler. The known cases are described below:

   1. When RadPdfViewer and the document are loaded initially and document is set through the RadPdfViewer.Document property.
Workaround: DocumentSource property could be set (in XAML or in code-behind) instead of the Document property. If the Document property is used, this should be done after RadPdfViewer is loaded.

    2. When the ScaleMode is changed in DocumentChanged event handler and then GoToPage() method is called in the same event handler.

When text is exported from PDF document using the TextFormatProvider (it's also used internally for the Copy operation), it is automatically split to lines using the vertical position of the words on the page, and small tolerance. 

Currently the tolerance is hard-coded to 0.1 pixels, which is not suitable for documents which contains scanned and OCR-ed text, and there the text lines could be slightly inclined. The result is that words on one slightly inclined line are recognized as if they are on separate lines.

This allows specifying a soft mask in the external graphics state.

"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.