Currently, this missing functionality may be workaround by either drawing the headers and footers with FixedContentEditor or by using RadWordsProcessing PDF export.

Page content is covered by overlay images after import-export due to lost text clipping.

Adding a table with the same code leads to different results 

When adding 10 identical tables onе or more have missing rows at the bottom. The seems to be caused by the text measurement. 

Handle documents containing invalid null entries in the optional content groups array.

Exporting a file with a Cmap and custom encoding results in an invalid file

When exporting with  TaggingStrategyType.Build, automatic table detection can include surrounding content in the table and generate rows, cells, and header associations that do not match the document’s logical structure. Headings may become table-cell content instead of remaining separate elements.

The exported PDF may pass automated accessibility validation despite having incorrect semantics for screen readers.

Provide a public API for setting the Scope attribute on explicitly created table-header (TH) structure elements.

Currently,  StructureElement.Attributes,  StructureElementTableAttributes, and  TableScopeAttribute are internal. Applications can create TH elements but cannot directly specify whether headers apply to a row, column, or both.

This prevents PDF/UA-1 compliance when table relationships are not defined through Headers and IDs.

Excessive text wrapping and row heights due to columns collapsing to excessively narrow widths when the total column width exceeds the table width.

Regression in versions after 2026.3.810.

Workaround: Manually readjust the column Width values.

Invalid structure tree triggers NullReferenceException instead of InvalidStructureTreeException.

Incorrect CID font resolution corrupts text after import-export.

Handle duplicate annotation references across pages during import.

Concurrent PDF export in a fresh process may hang, throw exceptions, or produce incorrect font embedding.

Add support for Linked Timestamp Correctness.

Add a setting to choose whether import continues or throws when invalid structure-tree data is detected. Default behavior continues import, skipping invalid entries without repairing them.

While signing a document in Adobe Reader, the users can lock the document fields from editing. Expose a similar functionality.

The feature is described by the FieldMDP transform method, described on page 736 from the Pdf Reference 1.7

Using the PdfStreamSigner to set signature Properties like Name, Location, Reason, and ContactInfo is not respected after export.

Add support for LT/LTA validation.

Add support for PAdES-B-LTA and renewal.

Add support for PAdES-B-LT / LTV evidence embedding.

Add support for conforming PAdES-B-B/B-T signing profiles.