The issue is caused by memory optimization that requires loading page content only for the visible pages. 

In order to fix the issue and still benefit from the memory optimization, we are introducing setter in FixedDocumentPresenterBase VisiblePages property. Now this property needs to be set each time the visible pages are changing in custom presenter implementation. Setting VisiblePages ensures that all visible pages content will be loaded correctly.

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.

The text appears disordered due to wrong calculations of the glyph geometries.

Add support for importing and filling interactive forms.

Interactive Forms content is visualized read-only in RadPdfViewer UI with R1 2017 Release

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.

The slow performance when creating thumbnail is only reproducible with specific documents.

Document cannot be loaded because the Encrypt property is not set and is null.

The performance of loading the thumbnails is decreased with the removing of the cache in PdfViewer. 

Possible reason is that the pages are no longer loaded asynchronously.

Steps to reproduce:
- Open the SDK with the thumbnails for PDFViewer.
- Notice that the load of the thumbnails is slow.

Add support for Lab color space. Currently alternate color is used to render the pixels, which may result in incorrect colors.

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.

If you search in a very large file and there are no matches of the string you're searching for or the matches are very far from the start (e.g. on the 10 000th page), the search takes a lot of time. The scenario can also lead to a crash.

Consider adding a progress bar showing on which page we're currently searching and implementing possibility to cancel the search.

The Form XObjects are supported in RadPdfViewer. In case anyone has messed up this feature with the one for interactive forms and form filling, please, vote and subscribe to the corresponding item at http://feedback.telerik.com/Project/143/Feedback/Details/197877 .

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.

When clicking on link annotations pointing to destinations in the document, and the "Fit one full page to window" mode is activated, the document is not scrolled exactly to the destination.

The issue can be reproduced only in Single Page Presenter mode and when the Top and Left values of the passed parameter are greater than 0.

The problem can also be observed by invoking directly GoToDestination method, as the problem is inside it.

I have a pdfviewer bound to a richtextbox like in your samples. But I want to keep the wpf viewer in fit to window scaling mode while changing the content of the richtextbox.

Right now the pdfviewer will rescale to 100 % on each update.