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 issue is reproducible only on Windows XP. On newer versions of windows, the images are rendered as expected.

WORKAROUND: You may inherit DctDecode class in order to implement custom decoder. For instance, you may try calling DecodeWithJpegDecoder method from the base class as mentioned in the note of this documentation article:

http://docs.telerik.com/devtools/wpf/controls/radpdfviewer/customization-and-extensibility/customize-pdf-rendering

A sample implementation of these custom decoder may be seen below:

public class CustomDctDecode : DctDecode
{
    public override byte[] Decode(PdfObject decodedObject, byte[] inputData, DecodeParameters parms)
    {
        return DecodeWithJpegDecoder(inputData);
    }
}

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

Currently the minimal zoom out value is 0.8% which impacts the performance while scrolling large documents.

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

When ScaleMode is set to FitToPage scrolling the Mousewheel or pressing the Arrow Down button does not produce immediate scroll. The page is scrolled to the next page after several scroll events/button presses are introduced.

Workaround: Provide custom ScrollCommand implementation.

This is reproducible when the matched result resides on different page.

Workaround: You may subscribe to the RadFixedDocument.CaretPosition.PositionChanged event and implement the scroll logic. Subscribe to PdfViewer's DocumentChanged event first if the document is not loaded.
        private void CaretPosition_PositionChanged(object sender, EventArgs e)
        {
            Telerik.Windows.Documents.Fixed.Model.RadFixedPage currentPage = this.pdfViewer.Document.CaretPosition.Page;
            int pageIndex = this.pdfViewer.Document.Pages.IndexOf(currentPage);
            this.pdfViewer.GoToPage(pageIndex + 1);
        }

Currently, we use System.Windows.Controls.TextBox for editing both TextBox and CombTextBox field types. We should implement CombTextBox editor which would allow having spaces between characters during the editing process.

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.

This would allow switching the focus between form field controls by using the Tab key.

This action is usually linked to a Button field and with it, the user of the application may revert all field values to their defaults. 

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.

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.

Currently, RadPdfViewer uses default constant value for the font size in this scenario.

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.