Instead, we should not visualize them and they should not be interactable with the mouse.

Fix available in LIB Version 2018.2.730.

When importing documents containing Interactive FormFields with an empty collection of Normal state appearances, a NullReferenceException is thrown, which leads to non-editable FormFields in PdfViewer.

Fix available in LIB Version 2018.2.730.

It seems that the glyph outlines are rendered wrong for some specific CFF font files. For instance, the issue is reproducible with "Aleo-Light" font.

When importing document containing a destination which points to invalid page reference, KeyNotFoundException is thrown.

RadPdfViewer can not find startxref keyword at the end of a document if the document contains many zero bytes at its end. NotSupportedException is thrown with "Startxref keyword cannot be found" message. 

Workaround: Trim the ending zero bytes before loading the document to the PdfViewer. This is currently noted in the WinForms KB article:
http://www.telerik.com/support/kb/winforms/details/notsupportedexception-startxref-keyword-cannot-be-found-when-loading-pdf-file-in-radpdfviewer-for-winforms

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.

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);
}

Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfViewer implementation.

Fix available in R2 2018 SP1 release version.

The width values from the widths PDF property should be taken with priority compared to the font file calculations.

Fix available in R2 2018 SP1 release version.

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 >>

This is caused by an incorrect order of applying the TextMatrix and the glyph stroking operation.

RadPdfViewer's AcroForm property ViewersShouldRecalculateWidgetAppearances should be respected when being set to true. In this case, RadPdfViewer should recalculate all widget appearances and this would resolve the issue with empty form field widgets after opening such PDF document.

An ArgumentException is thrown internally as the font name is null. However, the name is defined in the base font and can be obtained from it.

Fix available in LIB Version 2018.1.402.

This is reproducible when the field VariableTextProperties has zero value for font size. 

Fix available in LIB Version 2018.1.402.

This is not a valid PDF scenario as having appearance state requires having multistate appearances. However, we should handle this invalid document scenario on our side so that the app does not crash with NullReferenceException.

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.

The file contains the following:
68.637 604.561 455.981 -107.996 re
72.237 604.561 l
S
Instead of the more usual
68.637 604.561 455.981 -107.996 re
S
72.237 604.561 l
S
Both are valid but the first seems to create a problem.

Fix available in LIB Version 2018.1.319.

The exception is thrown when the RadioButtonField options array contains nested arrays instead of string values.

Fix available in LIB Version 2018.1.312.

This happens only in specific scenarios as most of the documents with annotations are visualized correctly.

When a PDF is printed all images are omitted.

Available in R1 2018 SP1 version.