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 is reproducible when the field VariableTextProperties has zero value for font size. Fix available in LIB Version 2018.1.402.
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.
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) ...
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 a ToUnicode CMap is defined for Simple Font (TrueType or Type1 font) which maps font character codes to two or more Unicode character values, the extracted text should contain the whole set of characters defined in the mappings. The current implementation of RadPdfViewer takes the first character specified in the ToUnicode mapping which leads to missing characters.
When the file has an annotation with a destination and this destination is missing from the destinations (Dests) collection of the catalogue, KeyNotFoundException is thrown when you try to scroll to the page where the annotation is located. A better behavior would be for nothing to happen when trying to click on the annotation leading to the destination.
This might result in invisible annotations.
This is not quite a valid PDF file scenario according to PDF file specification. However, we may try handling it in order to show the correct number of pages. When the kid is of type Pages, it should be added to the pages traversal recursion only the first time it is met.
The instances are kept in GeometryRenderer cache and each time the content stream is parsed new PathGeometry instances are added to GeometyRenderer store Dictionary field. Available in R1 2017 Official Release Version.
This may result in seeing the pattern as a solid color or even not seeing it at all if this color is white and coincides with the background of the page.
The UserDict collection is not parsed and the procedures for the operators are unavailable. The exception is thrown while trying to read the font file of the Univers and Univers Bold fonts. Internally, an ArgumenNullException is thrown, which results in missing content when the document is shown in RadPdfViewer.
The appearance of such invisible annotation is not imported property and the viewer is trying to recalculate it in an infinite recursion which causes the StackOverflowException. Fix available in LIB Version 2017.3.1009.
For some fonts the issue is present. Some of them are: KozGoPro-Medium KozMinPro-Regular KozGoPro-Bold
Setting Handle property to false should result in rethrowing the exception and interrupting current RadFixedDocument rendering. This is related to Exception Handling Mechanism mentioned in this documentation article: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/document-model/exceptionhandling
FixedDocumentSinglePagePresenter uses simple rendering mechanism using UIElements, which currently has some limitations: - Layers are not supported, thus annotations and forms are not rendered (even read-only) - UIElements could be affected (clipped) when UseLayoutRounding property set at parent level, when DPI is different that 96 DPI. Workaround: If content is clipped, ensure that UseLayoutRounding is set to false as presenter level: <telerikUI:FixedDocumentSinglePagePresenter UseLayoutRounding="False" />
When a page is rotated its annotations are not positioned correctly.
Currently, the implementation relies on the fact that the previous cross-reference value of a stream object is always a stream object. Instead during the cross-reference recursion, we should check on each step whether the previous cross-reference item is table or stream. Fix available in LIB Version 2017.3.1120.
This may result in inversed transparency issue when rendering images with ImageMask. Fix available in LIB Version 2017.3.1120.
The exception is thrown while decoding TIFF images. Although the document is properly loaded and the end user is not impacted, the DivideByZeroException is logged and present in the OnException event handler parameters.