When the first table row of each table (main as well as nested) has RepeatOnEveryPage set, the table header of the nested table overlaps the row on the new page.

When a DOCX document contains a table with fixed layout, and the table contains <tblGrid> element with improper widths (not coinciding with the ones visualized by MS Word), and such document is imported, the table is laid out with the width of the sum of the column widths imported from the table grid (tblGrid), instead of ones that could be correctly computed by the preferred width of the table cells. 



MS Word, for example, may ignore the widths specified in the tblGrid and compute new ones.



As a side effect, fixed-width tables can be laid out longer than their preferred width.

When the MoveToDocumentElementStart is called with parameter that is PermissionRangeStart and then is called a second time, the position moves to the previous position instead.

When the user copy-pastes an image from Outlook, it is pasted as an IncludePictureField and visualized as expected. The field code looks like

{INCLUDEPICTURE :image001.png@01D15D16.4FAF0970 \* MERGEFORMATINET}

However, when the fields in the document are updated, the image is no longer shown because of its invalid Uri. In MS Word, when you paste the image, it is directly inserted as image and the field is skipped.

Workaround - remove the field start/ends (in the attachments)

 

First Scenario: During layout of specific documents where the first section is with Continuous section break type, the layout algorithm enters in an infinite loop causing the application to hang.

Workaround: Change the section break type for the first section after the import of the document and before the layout:

Second Scenario: During the layout of specific documents where the last section is with Continuous section break type and has specific page size width and height, the layout algorithm enters in an infinite loop causing the application to hang.

Workaround 2: Slightly modify the size of the section which causes the issue after the import of the document and before the layout:

Third Scenario: During layouting of specific documents containing anchored elements, the layout algorithm enters in an infinite loop causing the application to hang. No workaround.

When custom annotations are created by inheriting AnnotationRangeStart and AnnotationRangeEnd classes, and the reaction to the delete commands is customized by overriding the DeleteBehavior, BackspaceBehavior, and DeleteSelectedBehavior, the delete command doesn't work as expected in some cases.

When exporting with RtfFormatProvider (including when the users copy content), an additional \par tag is added at the end of the document.

Workaround: Process the RTF after it is generated. 

Here is an example how to achieve it when copying:

this.radRichTextBox.CommandExecuted += radRichTextBox_CommandExecuted;
...
void radRichTextBox_CommandExecuted(object sender, CommandExecutedEventArgs e)
{
    if (e.Command is CopyCommand)
    {
        DocumentPosition end = this.radRichTextBox.Document.Selection.Ranges.Last.EndPosition;
             
        RadDocument clipboardDocument = ClipboardEx.GetDocument().ToDocument();
        RtfFormatProvider provider = new RtfFormatProvider();
        string rtfString = provider.Export(clipboardDocument);
        int indexLastParOpening = rtfString.LastIndexOf("{");
        int indexLastParClosing = rtfString.IndexOf('}', indexLastParOpening);
        string newRtf = rtfString.Remove(indexLastParOpening, indexLastParClosing - indexLastParOpening + 1);
        Clipboard.SetData("Rich Text Format", newRtf);
    }
}

The header of the first page can have only settings applied without any content. In such scenarios, RtfFormatProvider doesn't import the whole header, which can lead to a different layout of the document.

When a list is copied from one document (source) to another document (target) and the target contains custom list with different name, the paste command does not paste the list in the target.

Steps to reproduce:
1. Open two instances of RadRichTexbox
2. In the first RRTB create new list style -> List1 and use it to create a list
3. In the second RRTB create a new list style -> List 2 and use it to create a list
4. Copy the list from the second RRTB and try to paste it after the list in the first RRTB

Expected: The list is pasted.
Actual: The list is not pasted, but the list style is added to the List Library.

Some of the formatting symbols (e.g. space, tab) don't affect the height of the paragraph. With the current implementation, changing the font size of a formatting symbol, which is first in the paragraph, changes its height as well.

Applying a list does not follow the specified indention of texts. When a paragraph has previously applied indentation, it should be preserved and added to the indentation of the bullet. In RadRichTextBox, the indentation of the paragraphs is not respected when applying a list style to it - only the setting of the list is applied.

MS Word shows additional tab stop for a text in a list when a document is exported to RTF format.
Steps to reproduce:
1. Open RadRichTextBox
2. Add 2 or 3 paragraphs with text.
3. Add a 5-inch tab stop for those paragraphs.
4. Apply a list over those paragraphs.
5. Export to RTF format and view in MS Word.
Note: The paragraphs should not contain any tab symbols.
Observed result: MS Word shows additional tab stop at the start of the text in the list.

When the users move the image (evaluated as a result of the field) using the document selection, the field is removed from the document and the image is duplicated.

When a continuous section break is inserted on a page containing an image and with a watermark applied, the watermark is shown on top of the other document elements. The issue is observed only on the page with the section break.

Inserting a page break inside a table is currently not supported (the feature request is logged at https://feedback.telerik.com/Project/143/Feedback/Details/211108). Therefore, the Page Break button inside the Insert tab of the ribbon should be disabled when the caret is positioned inside a table.

Workaround: Track the position of the caret and when the latter goes into a table, set the Enabled property of InsertPageBreakCommand to false.

When an RTF document contains table inside table in the header or in the footer, the document cannot be imported due to NullReferenceException. In the case of RadRichTextBox the exception is handled, but it's not when RtfFormatProvider is used directly.

The bug is regression in 2016 R3.

When the document contains headings with heading styles associated with numbering styles (numbered headings), and TOC field is inserted and/or updated in the document, the TOC items should contain the numbering which comes from the style. Instead, on update the numbering is lost and only heading text is included in the field result.

InvalidOperationException is thrown in the IsInNonEditableRange() method of RadDocument when assigning a document to RadRichTextBox, which is created through the model and contains several read-only ranges.

Workaround: Call MeasureAndArrangeInDefaulSize().

When continuous section break is copied from RichTextBox and pasted to MS Word, it is inserted as Next Page break.

When section break between tables is deleted, the document structure gets corrupted and as a result, NullReferenceException is thrown after performing undo of the deletion operation. 
As a workaround PageBreak could be used instead of Section break.