When importing a document containing Outlines (Bookmarks) containing Actions with an empty dictionary:

<</Title(Bookmarks)/Parent .../First .../Last .../Prev .../A<<>>/Count ...>

leads to an exception thrown: System.MissingMethodException: 'Cannot create an abstract class.'

Hi Telerik Support

We use your Telerik PDF-Viewer since your last Version "UI for WPF R1 2021" which supports Type 3 fonts.
Now the version runs productive by our customers. But after a day, they found some special PDFs that doesn't work quite right with your PDF-Viewer.

In the appendix you will find the PDf-Files as samples for the bugs that i'm describing.
Because of data privacy, the PDF-Files are cutted and cropped.
Also a demo project is appended (It could also be reproduced with the demo Progress Telerik WPF UI for th PDF-Viewer).

First Problem: Blank Page

Hint: It seems that only a few PDF-Files from a specific program seems to be a problem.

1. Open Demo "WpfAppPdfViewer.exe"
2. Open the file sample_1_blank_page.pdf(see appendix)
3. You will see only a blank page
4. Open the same PDF-File in another PDF-Reader like Adobe Reader and you will see a scan with an illegible stamp of an address

Second Problem: Displaying data delayed

1. Open Demo "Progress Telerik UI for WPF"
2. Open the file sample_2_delayed_display.pdf (see appendix)
3. You will see only a blank page
4. Wait approx. 5-10 sec. and you will see the content of the PDF-File.

I would be glad for a quick possible solution for our customer.

Best regards

Serge Schoop

Currently, the PdfProcessing document model is providing support only for a single function in the Function entry.

According to the PDF Specification: Function: A 1-in, n-out function or an array of n 1-in, 1-out functions.

Creating a PdfViewer instance without adding it in the visual tree, leads to leaked document presenter instances when the TouchManager is enabled.

Workaround: Disable the TouchManager:

Telerik.Windows.Input.Touch.TouchManager.IsEnabled = false;

Inserting PNG ImageSource into a document and applying the document instance directly to the RadPdfViewer`s Document property (without exporting to stream) leads to a wrong image rendering.

Workaround: Export the document with the PdfFormatProvider:

MemoryStream ms = new MemoryStream();
PdfFormatProvider pdfFormatProvider = new PdfFormatProvider();
pdfFormatProvider.Export(radFixedDocument, ms);

PdfDocumentSource source = new PdfDocumentSource(ms, pdfViewer.DefaultImportSettings);
this.pdfViewer.DocumentSource = source;

When importing a document containing a single associated widget annotation merged into the field dictionary the field is skipped on import and an exception is thrown.

According to the PDF Specification: Field Dictionaries: Kids:

An array of indirect references to the immediate children of this field.
In a non-terminal field, the Kids array is required to refer to field dictionaries that are immediate descendants of this field. In a terminal field, the Kids array ordinarily must refer to one or more separate widget annotations that are associated with this field. However, if there is only one associated widget annotation, and its contents have been merged into the field dictionary, Kids must be omitted.