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.

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

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.

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

When Find Next is used multiple times fast, and pages are still loaded asynchronously, sometimes NullReferenceException is thrown with the following call stack:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.GetLastCharacter()
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.IsLineBreak(Glyph glyph)
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.ProcessGlyph(Glyph glyph)
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.CreateTextPage(RadFixedPageInternal page)
   at Telerik.Windows.Documents.Fixed.Text.TextDocument.GetTextPage(Int32 index)
   at Telerik.Windows.Documents.Fixed.Search.KMPTextSearch.FindNext(TextDocument document, TextPosition startPosition, String searchText, Boolean matchCase, Boolean wholeWordsOnly)
   at Telerik.Windows.Documents.Fixed.Search.TextSearch.Find(String text, TextSearchOptions options)

...

A similar scenario is not defined in the PDF specification but the widgets can be rendered as read-only fields despite the fields associated with them are missing.

This is Unicode (UTF-16BE) encoding for the Adobe-GB1 character collection; contains mappings for all characters in the GB18030-2000 character set.

Described on page 443 in Pdf Reference 1.7.

This might result in invisible annotations.

When using the Fluent theme and the NoXaml binaries the above mentioned design time exception is thrown.

The current page changes too late, almost when the whole page is out of the view. This behavior is wrong making the page number showing the previous page when actually a new one is in the view. It should change when the second page visible height is higher than the current page visible height.

The offset of the CropBox is not respected and is always treated as 0.

Workaround: Import the document with PdfProcessing, change the CropBox offsets of the pages to 0, export the modified document and then import it in PdfViewer.

Right now an exception is not raised for gruop3 2d encoding.

When RadPdfViewer is created on UI thread different than the Application main thread, an InvalidOperationException: 'The calling thread cannot access this object because a different thread owns it.' is thrown when calling the Copy method.

Use the attached project to reproduce. 

Workaround:

var combo = toolbar.ChildrenOfType<PercentComboBox>().FirstOrDefault();

var binding = new System.Windows.Data.Binding();
binding.Path = new System.Windows.PropertyPath("ScaleFactor");
binding.Mode = System.Windows.Data.BindingMode.TwoWay;
binding.Source = pdfViewer;
binding.UpdateSourceTrigger = System.Windows.Data.UpdateSourceTrigger.PropertyChanged;
BindingOperations.SetBinding(combo, PercentComboBox.ValueProperty, binding);

var binding1 = new System.Windows.Data.Binding();
binding1.Source = pdfViewer;
BindingOperations.SetBinding(combo, PercentComboBox.RadPdfViewerProperty, binding);

When importing the document as DocumentSource the stream will be loaded asynchronously and the document won't be loaded when the Print() method is called, NullReferenceException 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.

User is not able to type in the form fields on touch devices.

After saving a document from PdfViewer, it cannot be opened by other applications as it is still locked.

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

When importing a document containing an ICCBased color space an exception is thrown.