The viewer is using a large amount of memory when scrolling a specific PDF file. After some point, an OutOfMemeory exception is thrown.

Workaround:

Build for the x64 platform

The executing of the PostScriptReader`s Read method takes a lot of time when iterating content streams with many Path geometries.

A specific scanned file is not displayed with the new model.

When importing document with text containing char code mapped to .notdef glyph name an ArgumentException: 'The encoding is not supported.' is thrown.

When saving Form Fields in document defined with linearized PDF structure, it produces a document that fails to open in Edge.

When importing a document with empty pages collection an ArgumentNullException: 'Value cannot be null.
Parameter name: page', is thrown, which leads to application crash.

I am using the PDFViewer control in a VisualStudio VB.NET application. The PDF is not showing all the details as it appears in Adobe PDF Reader. In particular, the text is not showing up (but is highlighted when selected) and there is gray shading that is not visible. See attached sample file. Please advise.

When the Interactive Form Fields are in read-only mode, the user should not be able to change the value of the field. The associated Form Field widgets should not interact with the user, e.g. they should not respond to mouse clicks or change their appearance in response to mouse motions.

Please refer to the attached sample screenshot demonstrating how the document look in Adobe and in RadPdfViewer.

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

Currently, Tab selects the next control.

Attached is sample PDF document. 

Currently, RadPdfViewer uses WPF DrawingContext class for drawing page elements to a Canvas.  When PDF page has many content elements (usually geometries) drawing the page may be time-consuming and freezes the UI. 

Instead, we should consider implementing another approach for rendering the content asynchronously which would improve the user experience. 

structure
The hierarchical document structure is a means to describe the PDF document structure, which is currently not supported. See 10.6.1 Structure Hierarchy on 856 page of the PDF specification for details.
This document structure is an alternative to the standard PDF structure and most non-Adobe software does not support it.

The document might have been created with Adobe software like Adobe LiveCycle Designer. Very often the document contains some fallback text in the standard PDF structure like:
"Please wait... If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document."
"The document you are trying to load requires Adobe Reader 8 or higher. You may not have the Adobe Reader installed or your viewing environment may not be properly configured to use Adobe Reader. For information on how to install Adobe Reader and configure your viewing environment please see  http://www.adobe.com/go/pdf_forms_configure."
"For the best experience, open this PDF portfolio in Acrobat X, Reader X, or later."

When the file has an annotation with a destination and this destination is missing from the destinations (Dests) collection of the catalogue, KeyNotFoundException is thrown when you try to scroll to the page where the annotation is located. A better behavior would be for nothing to happen when trying to click on the annotation leading to the destination.

When there is no ToUnicode CMap, the text from the Simple Font instance (TrueType or Type1 font) should be extracted by mapping the glyph name to its corresponding charcode according to Adobe Glyph List. Additionally, the Differences array should be included in these calculations when there is custom encoding. The current implementation of RadPdfViewer makes ToString to the original char id byte value which leads to wrong characters. 

More information about this may be seen in the second point of section "5.9.1Mapping Character Codes to Unicode Values" on page 470 in PdfReference 1.7.

The rendering of images with size ~5000/6000 and BitsPerComponent is time-consuming. The scenario is optimized in terms of memory but would be nice to increase the performance as well.

While the other annotations are drawn on top of the content, the highlight annotation is behind the text it highlights. In other words, it has to be inserted at a specific place in the ContentElementsUILayer. The pdf seems to mark the precise place where the highlight should be placed with the BDC, MCID and EMC operators in the content. At the moment, the read-only rendering of the highlight annotation has been implemented with an instance of the AnnotationUILayer called "HighlightUILayer" which is placed behind the ContentElementsUILayer. With this implementation, depending on the contents of the pdf, the highlight annotation might be visible or it might not be. 

To reproduce:
- Drop a RadPdfViewer on a blank form at design time. 

Some documents reqire this assembly as well.