This missing functionality may be workaround by implementing and registering custom IPdfFilter implementation that decodes JPEG2000 images. The custom decoder may be registered with FiltersManager class and its implementation may be similar to RadPdfViewers JpxDecoder SDK example implementation:

- https://github.com/telerik/xaml-sdk/blob/master/PdfViewer/CustomDecoder/JpxDecoder.cs
- Use a custom JPXDecode filter with RadPdfViewer

Support for validating signature fields signed with signatures that are encoded in ETSI.CAdES.detached encoding should be added.

InvalidCastException is thrown when importing a PDF with a CR-terminated comment in its /Info dictionary.

PDF export fails after HTML blocks containing empty or named anchors are imported and inserted into a RadFlowDocument through ReplaceText.

HTML importer creates hyperlink field markers for <a name="...">. During block replacement, cloned FieldCharacter instances lose FieldInfo, leaving orphan field markers. PDF exporter later dereferences FieldInfo and throws a NullReferenceException.

The values of rotated widgets on a rotated page are invisible after exporting them. The value can be seen only while editing a field.

Wrapped table cell text is incorrectly split by hyphens ("-").

This is a regression introduced in version 2026.3.826. Use an older version to avoid this issue.

Currently, font registration APIs accept only byte[], requiring callers to load the entire font file into memory before passing it to the library. This can be problematic for large font files, especially CJK fonts, which can significantly increase application memory usage.

When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly.

There are many instances of the internal Transition, State and ImageXObject classes.

InvalidOperationException: 'isContentReleased' is thrown when appending pages with shared image content to a new document using the PdfStreamWriter.

When two PDFs containing AcroForm fields are merged with PdfStreamWriter, the generated PDF contains page widget annotations whose parent field dictionaries are not correctly registered in the document-level /AcroForm/Fields tree.

The issue is reproducible by merging the same four-page form twice. The resulting PDF contains all widget annotations, but PDF viewers do not resolve the second form’s interactive fields correctly.

Endless loop on PDF export when an empty string is assigned to text fields with no source /V and auto-sized default appearance (/DA with 0 Tf).

Workaround: Instead of an empty string (""), set the value to null. Or don't set it at all and leave it unmodified.

Missing/corrupted font characters during multithreaded PDF export.

Error 141 TYPECHECK on Lexmark printer when printing DPL-generated PDF file.

Merging/importing PDFs with duplicate field names can create one logical RadioButtonField containing widgets from multiple source field nodes. The first node initializes its widget options. Reused duplicate nodes can add additional widgets without assigning RadioOption instances.

The widgets then contain valid "/Off" appearance states, but their model Option property is null. During export, FieldPropertiesExporter accesses widget.Option.Value, causing a "NullReferenceException: Object reference not set to an instance of an object."

If the MatrixPosition has Matrix (1, 0, 0, 1, 20, 10) the Table should be positioned with top-left coordinate (20, 10). Instead, it is wrongly positioned at (40, 20).

InvalidCastException is thrown when importing a document that contains structure elements (StructElem) with StructureType (/S) defined with an incorrect integer type (PdfInt) instead of the expected PdfName type.

When a row has two cells and the content of the first one is large, the width of the second cell results in too small value while measuring and its content remains invisible.

Workaround: Set PreferredWidth to the second cell.

If a PDF with a TextBoxField is created with a corresponding Widget, the text is actually long enough to be broken in more than one line and AllowScroll is set to true, upon opening the file in Adobe, the text is not visible. The field actually does have an appearance which can be seen upon inspection of the document but for some reason it is not visualized.

Another issue seems to be a different manifestation of the same problem: When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly. 

When signing a PDF document with an image using the PdfStreamSigner, the signature is broken. This is the used approach for signing the document: https://www.telerik.com/document-processing-libraries/documentation/libraries/radpdfprocessing/features/digital-signature/pdfstreamsigner

However, instead of using the DrawText method, the DrawImage method is used.