A NullReference exception is thrown when the content of a MS Outlook mail is copy/pasted into RadRichTextBox. 

This is reproducible in Paged LayoutMode.

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 the caret position is inside Table and a page break is inserted, the table should be split into two tables with a page break between.

Create document with some text.
Insert image.
Right click on image and add hyperlink to it.
Drag the image somewhere in the text.
Observe that it is created a copy of the image. 

Actually, the issue occurs when the hyperlink is inserted.

When there isn't space for the first non-repeated row to be drawn on the page, the repeated rows should not be repeated on each page where the table spans - they should be drawn only on the first page (the page where the table begins). 
 
However, currently the requirement described above is not satisfied and the first repeated row is drawn on every page, where the table spans, which is not correct according to the Office Open XML specification. 

If you highlight a section of text and apply styles to it like bold/italic/underline and place your cursor at the end of that text the Clear All Formatting button does not work. If you turn on those styles and then type some text and place your cursor at the end of that text it does work. The difference in the XAML is that in the first case the styles are only on the span of text itself while in the second the styles are on the span and the paragraph. I have attached a GIF of steps to reproduce and the XAML from the editor before clicking the Clear All Formatting button.

Expose an API allowing easy customization of the layer.

Currently, working with bookmarks and cross references in the headers and footers of a document is not supported.

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);
    }
}

Currently, when the users perform replace, and there are no more matches which should be replaced, the "The searched text was not found" message is shown. Add functionality to say that there are no more matches instead of saying that the text is not found.

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.

The RTF specifications states that the header of the document should start with "\rtfN" where N is the version of the RTF. Currently, the RtfFormatProvider do not save the version, but only "\rtf". Most software handles this case, but in some cases the document cannot be read.

Provide option for configuring the measurement units (centimeters [cm], inches [in]) used throughout RadRichTextBox UI, including:
- Ruler (currently supported and configurable through DocumentRuler.MeasurementUnit property which is of type UnitTypes)
- Table dialogs - for indents, widths and heights
- Paragraph indentation (currently shown only in points [pts])
- Section properties - header from top and footer from bottom
- Page setup - columns width in Columns dialog
- Page Margins and Page Size in Ribbon UI

Currently parts of the dialogs and controls shows measures in pixels (actually DIPs), other in inches (e.g. ruler).

When dragged from the toolbox, the wizard adds only <telerik:RadRichTextBox /> tag and does not generate XAML for the Ribbon UI. 

Workaround: On second attempt, the UI of the ribbon is generated as expected. Note: The generation is not working in Visual Studio 2017, even on the second attempt.

Available in R1 2018 Official Release version.

Provide option for exporting InlineUIContainer and FloatingUIContainer as images to docx and RTF format.

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.

Implement advanced find dialog similar to MS Word which provides an option to search for paragraph end marker, tab character, and others.

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.