At this point, the Print() method allowing the customers to silently print a document uses the PrintableAreaWidth and PrintableAreaHeight properties of the print dialog, which are read-only and cannot be changed through the API. Consider changing them with PrintTicket.PageMediaSize.

We should also consider the scenario when the client needs to print a smaller PDF page on a bigger page size. For instance, A5 page to be printed on an A4 sheet without scaling the content.

This is reproducible for images with FlateDecode and predictor value in the range between 10 and 15. As an example you may take a look at the DecodeParms property in the following image PDF dictionary:

<< /BitsPerComponent 8 /ColorSpace /DeviceRGB /DecodeParms << /BitsPerComponent 8 /Colors 3 /Columns 1024 /Predictor 15 >> /Filter /FlateDecode /Height 2868 /Subtype /Image /Type /XObject /Width 1024 /Length 1236707 >>

The current implementation relies on valid cross-reference table offsets in the PDF documents so that PDF objects are easily found and parsed. However, a mechanism for importing documents with invalid cross-reference table offsets may be implemented.

The attached project shows how to repair such documents.

The position of annotation text is not calculated as expected with a specific setup of its bounding box.

Handle the cases when the page is rendered slowly and the document appears empty

When specific culture is set (e.g. Hebrew but not only) in a project targeting .NET 5 (or later), some documents are not rendered correctly (rendered as blank pages).

Some of the lines that should be dashed are rendered as continuous lines.

Currently, when printing landscape pages the content is rotated clockwise. There has to be an option to set it to anti-clockwise.

The default WPF PrintDialog cannot print asynchronously when it is shown in UI. However, you may see the demo in this forum post showing how to create custom PrintDialog and perform async printing with it:
http://www.telerik.com/forums/pdfviewer-print-makes-ui-unresponsive#js0YdzFWc0Oa8C3g6a18lg

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.

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

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

When there is no ToUnicode CMap, the text from the Simple Font instance 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. 

The document will be imported with a loss of content. The reason is that ASCII85Decoder will throw an ArgumentException when the stream doesn't end with '~>'. 

Although this is invalid case according to PDF specification, other applications are handling it and the document is successfully visualized in them. We may also consider implementing workaround that handles such invalid streams.

As a result, the glyphs are not measured and positioned properly. The issue applies to the TrueType and Type1 fonts.

This exception seems to be related to AES algorithm PaddingMode property. 

This happens only in scenarios when the widget has On state appearance defined and Off state appearance missing. If both appearances are missing then RadPdfViewer recalculates the appearances and the checkbox is successfully selected and deselected.

When modifying Interactive Forms TextBoxField's value the entered changes are preserved after is clicked out of the TextBoxField's editing area. However the changes are not applied when the click is performed on the save button.

As possible workaround you can raise a MouseLeftButtonDown event on the RadPdfViewer and after this execute the SaveAsCommand. For example:

private void SaveButton_Click(object sender, RoutedEventArgs e)
{
    MouseButtonEventArgs mouseEventArgs = new MouseButtonEventArgs(Mouse.PrimaryDevice, 0, MouseButton.Left)
    {
        RoutedEvent = FrameworkElement.MouseLeftButtonDownEvent
    };
 
    ((FrameworkElement)this.pdfViewer.FixedDocumentPresenter).RaiseEvent(mouseEventArgs);
    this.pdfViewer.CommandDescriptors.SaveAsCommandDescriptor.Command.Execute(null);
}