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

Wrong calculations of new lines and white spaces between characters due to a wrong calculated character`s BoundingRect.

This results in missing whitespaces and/or characters split between lines.

When merging PDFs containing byte-identical RGB image streams with different /SMask images, PdfStreamWriter reuses one image object and its mask. Signatures, stamps, or other masked images then render with incorrect transparency or shape.

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

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

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.

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

When creating a GradientStop, an alpha channel of the color could be applied. However, this setting is not respected it the result document and the gradient is with full opacity.

Steps to reproduce:
1. Create a gradient with an alpha channel:

RadFixedDocument document = new RadFixedDocument();
RadFixedPage page = document.Pages.AddPage();
FixedContentEditor containerEditor = new FixedContentEditor(page);

LinearGradient linearGradient = new LinearGradient(new Point(0, 0), new Point(30, 30));
linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 207, 0), 0));
linearGradient.GradientStops.Add(new GradientStop(new RgbColor(10, 0, 102, 204), 1));

containerEditor.GraphicProperties.FillColor = linearGradient;
containerEditor.DrawRectangle(new Rect(10, 10, 48, 29));

2. Export the document to PDF

Observed: The alpha channel is not respected and the gradient is with full opacity

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.

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. 

As one can use annotations we should support attachments per page or per pdf-file.

The use case we should cover is make stamp or other signatures immovable.

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.