When the document instance is changed (setting RadRichTextBox.Document property to new RadDocument instance), the old document is not released from the memory. There are UI providers, which are not properly removed from the layer's collection.

The issue is regression, introduced in R3 2016.

Workaround 1: Subscribe to DocumentChanging and set the layout mode of RadRichTextBox to Paged. Reset it back to Flow on DocumentChanged.

void radRichTextBox_DocumentChanged(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Flow;
}

void radRichTextBox_DocumentChanging(object sender, EventArgs e)
{
    this.radRichTextBox.LayoutMode = DocumentLayoutMode.Paged;
}

Workaround 2: Remove the WatermarkUILayer. You can achieve that by creating a custom UILayersBuilder. For more information on this approach, check the help article at http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/how-to/features-custom-ui-layers

protected override void BuildUILayersOverride(Telerik.Windows.Documents.UI.IUILayerContainer uiLayerContainer)
{
    base.BuildUILayersOverride(uiLayerContainer);
    uiLayerContainer.UILayers.Remove(DefaultUILayers.WatermarkLayer);
}

Fix available in LIB Version 2017.2.724.

When the LayotMode of RadRichTextBox is set to Flow and a Table is inserted as the first element in this document, the adorner icon is cut off by the document edge and cannot be used.

The bullets can have their own alignment. Implement import and export of this setting.

Expanding the table selection with the keyboard leaves the caret behind the selection's edges. After we pass the current cell content, the selection is automatically broadened over the next complete cell, but if we continue to press Shift+Arrow, it takes keystrokes = length of content in the cell + 1 to expand the selection to its next cell, though the selection highlights are already covering that cell.

There is a workaround: you will need to subscribe to the SelectionChanged event and use this code snippet for the event handler:

private void SelectionChanged(object sender, EventArgs e)
{
    var selection = this.radRichTextBox.Document.Selection;
    var caretPosition = this.radRichTextBox.Document.CaretPosition;

    if (selection.IsEmpty)
    {
        return;
    }

    if (selection.Ranges.Last.IsReversed)
    {
        caretPosition.MoveToPosition(selection.Ranges.First.StartPosition);
    }
    else
    {
        caretPosition.MoveToPosition(selection.Ranges.Last.EndPosition);
    }
}

Inside it, we move the caret to the selection's edges.

When some cells are merged in one cell and context menu is displayed for the merged cell, "Merge Cells" option is still available in the menu. However it should not be available for a merged cell.

The vertical text alignment in repeated table header row is not consistent with the first row.

Please check the attached screenshot.

Available in LIB Version 2017.2.619.

The InsertTable command should copy the current style to all paragraphs in the new table.

Tabs button in Paragraph Properties dialog is visible even when RadRichTextBox.TabStopsPropertiesDialog is not set. In addition, pressing the button in this scenario closes the Paragraph Properties dialog itself.

As this property is automatically set using MEF, this situation could happen if the tabs dialog is missing in the the composition container.

Workaround: Check whether the TabStopsPropertiesDialog is null and if true, then hide the TabsButton:

    var windowTabStopsPropertiesDialog = (this.radRichTextBox.TabStopsPropertiesDialog as RadWindow);
    var windowParagraphPropertiesDialog = (this.radRichTextBox.ParagraphPropertiesDialog as RadWindow);
    if (windowTabStopsPropertiesDialog == null)
    {
        (windowParagraphPropertiesDialog.FindName("TabsButton") as RadButton).Visibility = Visibility.Collapsed;
    }

When symbol is inserted in underlined word, the underline color of the inserted symbol is always black and doesn't respect the underline color of the word.

Also, when Track Changes is ON and some symbols are inserted, the underline color is black instead of being red. Probably the root cause is the same for both behaviors.

When misspelled word is corrected with the spell checker, and the word is just before the comment range end, the comment range end is moved after the previous word.

Steps to reproduce:
1. Open RichTextBox and type the following sentence: "This sentence has a wrong speling".
2. Select the entire sentence and click "New Comment" button.
3. The comments range start marker displays before "This...." and comment range end marker displays after "...speling"
4. Right click on word "speling" to change "speling" to "spelling"
Result: The spelling gets fixed as expected, but the comment range end moves before the word "spelling".

The fix will be available in our next LIB release (v. 2016.1.208).