The form fields are not displayed when loading specific pdf files.

If the appearance is defined using a non-existing object reference in PDF document, NullReferenceException is thrown on import. 

Some documents containing embedded jpeg images with DCTDecode filter are not decoded correctly in RadPdfViewer for Silverlight

JavaScript actions causes a script to be compiled and executed by the JavaScript interpreter. Depending on the nature of the script, the values of the interactive form fields in the document can be validated or updated or the visual appearances of the fields can be changed.

This is reproducible only with specific documents which reuse big images content throughout pages.

Available in LIB Version 2018.1.205.

The issue occurs only in Silverlight and only when the glyph is filled with tiling pattern brush.

Fix available in LIB Version 2017.2.808.

You could repair the invalid file using the project from the attachment.

This will allow import of Tensor-product patch mesh gradients.

The fix will be available in our official release Q2 2015 SP.

Available in R1 2017 Release

The reusable Form XObject content always resets its GraphicState color property. Instead, it should take the current GraphicState color from the content stream. This may result in wrong colors.

The character mapping cannot find the character with name "checkbld" and the glyph is not visualized.

The character is rendered with different glyph geometry and wrong glyph width which results in overlapping text.

The fix will be available in our official release 2015 Q2.

The colors are different everytime the file is opened in the viewer.

Available in R1 2017 Release

When you have a text box in a custom layer, the page presenter gets the focus and does not allow you to focus the text box.

The fix will be available in our official release 2015 Q2. 

The fix will be available in our latest LIB release (v. 2015.1.0323).

This item is declined because it is wrongly logged and the issue is duplicated with another feedback item. You may follow instead these feedback item which also provides a sample attached project for repairing such invalid files:

https://feedback.telerik.com/Project/143/Feedback/Details/170586-pdfviewer-handle-documents-containing-invalid-cross-reference-table-start-index