Importing a document, which contains pages with many geometries - such as paths, lines, and curves leads to degraded scrolling performance.

A shape is draw incorrectly when showing a specific file

The read-only flag is not respected when importing a document

Using Adobe the edit mode is triggered on the first mouse click.

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.

The current implementation of the RadPdfViewer Save uses the incremental update feature. However, the incremental update doesn't comply with the linearized structure and the document fails to open in some viewers.

Workaround: Import/export the document with PdfPRocessing to remove the linearization feature.

The offset of the Page boundaries such as CropBox, MediaBox, BleedBox, and ArtBox is not respected and is always treated as 0 which causes misplaced Annotations.

Visualizing a page with a huge number of images (40000) freezes the application.
When switching to the FixedDocumentSinglePageViewPresenter, all the page content should be loaded so it can be later rendered. Although the images are loaded asynchronously, there are too many threads started which seems to cause the hang. Also, according to profiling results, it seems like the image caching causes performance diminishments in such scenarios. 

When the font is not embedded in the document, PdfViewer tries to read it from the OS. However, the Calibri-Font is not properly parsed and a NullReferenceException is thrown internally for its encoding. 

The stroke is not rendered when the text is in XForm

To reproduce:

- Search for a specific word until the last occurrence is found and a message appears. 

- Click the FindPrevious button

Result: A message appears.

Expected: The previous entry is selected. 

Document with invalid cross-reference stream is not loaded correctly

Unsupported annotations are rendered on top of other content. When there is a form field that appears inside the annotation, it cannot be clicked or interacted with as the annotation is capturing the mouse gestures.

WPF controls are used to visualize the form fields in PdfViewer. However, these controls inherit the background defined in the PdfViewer's theme instead of a background of the form field control. This leads to wrong visualization mostly in the dark themes as the content inside the form field might get unreadable.

Documents containing large images are slow to decompress and decode.

The character is visualized as '3'. The same issue is also reproducible when the content is copied from Adobe.

Loading document containing link with no destination leads to ArgumentNullException in PdfElementToFixedElementTranslator.CreateDestination method.

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

Workaround: Import the document using the PdfProcessing library and add an empty page:

 

The CIDFont dictionary may contain an array, describing the widths of the glyphs. If the width has a negative value an ArgumentException: 'Width and Height must be non-negative.', is thrown when the document is imported in RadPdfViewer, which leads to application crash.

By specification, the InteractiveForm fields can have the same name if they are descendants of a common ancestor. Such fields are different representations of the same underlying field; they should differ only in properties that specify their visual appearance. When such a document is imported an ArgumentException: 'An item with the same key has already been added.' is thrown, which leads to non-editable fields in RadPdfViewer.