Bold is not reset when creating a bullet line on a new line 

The memory leak is reproducible when the main thread is too busy to dispose objects used by RadDocument internally. Thus, the RadDocument instances are kept alive in the memory. 

Workaround: When the scenario includes back processing of documents: Start different threads responsible to perform the required operations and use the following code:

Dispatcher dispatcher = Dispatcher.CurrentDispatcher;
dispatcher.BeginInvokeShutdown(DispatcherPriority.Normal);
Dispatcher.Run();

anywhere in the background thread processing the RadDocument.

- When a floating image is inserted into header/footer the image is clipped. However, if Enter is pressed in the header/footer later, the whole image is shown. Further, if Enter is pressed again, the image is clipped again.
- When floating images are placed in a header or footer, and are positioned outside of the text editor's area, they are not visualized. MS Word visualizes such images as slightly grayed out (similar to watermarks) in normal mode, and always visualizes them in Header/Footer edit mode.

When comment is inserted in the document, keyboard focus is not moved to the comment, and when the users start typing, they actually override the comment range in the document.

RadRichTextBox.TabIndex property does not have effect. The TabIndex will remain at maximum and RadRichTextBox will be last in the tab order. Moreover, setting RadRichTextBox.IsTabStop to false also doesn't have effect.

The issue is showstopper for the cases where RadRichTextBox is used along with other controls.

When the current SpanLayoutBox is split (for example by inserting space), the DocumentPosition created with trackDocumentChangeEvents option (with some of the constructor accepting the boolean 'trackDocumentChangeEvents' parameter) jumps back with two symbols.

If header/footer containing annotations is set to a document using RadDocumentEditor.ChangeSectionHeader or ChangeSectionFooter methods, the annotations in the body of the header/footer are not paired in the resulting document.

When such document is exported to XAML, NullReferenceException is thrown in the ReindexAnnotationMarkers internal method.

Workaround:
- Do not use RadDocumentEditor to set the footer:
//editor.ChangeSectionFooter(radDocument.Sections.First, HeaderFooterType.Default, new Footer { Body = footerRadDocument });
radDocument.Sections.First.Footers.Default.Body = footerRadDocument;

- Manually "fix" the cloned footer body before the export:
((ISupportInitialize)radDocument.Sections.First.Footers.Default.Body).EndInit();

The built-in Hyperlink style is not applied to hyperlinks imported from HTML (<a> tag). As a result, the hyperlinks in the document do not have the blue underline.

Workaround: Subscribe for the SetupDocument event of the HtmlDataProvider and set the hyperlinks' style manually.
private void HtmlDataProvider_SetupDocument(object sender, Telerik.Windows.Documents.FormatProviders.SetupDocumentEventArgs e)
{
    StyleDefinition hyperLinkStyle = e.Document.StyleRepository[RadDocumentDefaultStyles.HyperlinkStyleName];
    hyperLinkStyle.SpanProperties.ForeColor = Colors.Green;//Color.FromRgb(0xff, 0x7a, 0xcc);
    var hyperlinks = e.Document.EnumerateChildrenOfType<HyperlinkRangeStart>();

    RadDocumentEditor editor = new RadDocumentEditor(e.Document);
    editor.Document.History.IsEnabled = false;

    foreach (HyperlinkRangeStart hyperlink in hyperlinks)
    {
        e.Document.Selection.SelectAnnotationRange(hyperlink);
        editor.ChangeStyleName(RadDocumentDefaultStyles.HyperlinkStyleName);
    }
    e.Document.Selection.Clear();

    editor.Document.History.IsEnabled = true;
}

When an enter is pressed the paragraph is split into two parts and does not apply the current editing style to the formatting symbol of the first part.

Steps to reproduce:
Add text to an empty paragraph.
Increase the font-size.
Press enter.

Expected result: If the user starts to write the text should have its font properties from the current editing style. 

Expected result 2: If the client moves the caret around and then return to the beginning of the second paragraph it and start writing, the text should have its font properties from the formatting symbol(which are applied from current editing style when the paragraph has been split). 

Invoking the same Paste Options command for a second time does not close the popup. It is closed when another Paste Options command is executed.

When the popup is located on the bottom side of the document and it is also close to the end of the presenter and a user opens it, then the popup goes outside the area.

Popups (ImageMiniToolBar and SelectionMiniToolBar) stay on most top (act as if "Always on Top" is set to them) even if they had lost focus. 

Workaround: Attach to LostFocus or LostKeyboardFocus events and hide the toolbar in the handler:
this.radRichTextBox.LostFocus += (sender, e) =>
{
    this.radRichTextBox.SelectionMiniToolBar.Hide();
    this.radRichTextBox.ImageMiniToolBar.Hide();
};

This causes some problems if the hyperlink is edited and the document is exported and imported again.
Workaround:
private void RadRichTextBox1_DocumentChanged(object sender, EventArgs e)
{
    var document = radRichTextEditor1.Document;

    var fields = document.EnumerateChildrenOfType<FieldRangeStart>();

    foreach (FieldRangeStart item in fields)
    {
        radRichTextEditor1.DeleteAnnotationRange(item);
    }
}

When a table is on a page different than the first one and user clicks on the thumb for resizing the table row height, wrong value is calculated and passed to the setter of the TableRow's Height property.

This leads to wrong table layout when the document is exported using RtfFormatProvider.

When the preferred width of the table is set to a percentage value and the columns inside have preferred width values in pixels, the bigger width should take precedence when showing the table. At this point, the table column widths are with higher priority.

The ImagesDeflaterCompressionLevel and ContentsDeflaterCompressionLevel in the PdfFormatProvider's export settings have 0 for default value instead of -1.

Workaround: Change the settings's properties to -1 explicitly.

When image watermark is set and its height is configured through DocumentWatermarkSettings.ImageSettings.Size.Height, the height is not respected.

Steps to reproduce:
1. Insert a Watermark with size
           var watermarkSettings = new DocumentWatermarkSettings()
            {
                Type = WatermarkType.ImageWatermark,
                ImageSettings = new WatermarkImageSettings()
                {
                    UriSource = new Uri("c:\1.jpg"),
                    Size = new Size(200, 300)
                }
            };

Expected: The image is with the specified width and height.
Actual: The height is different.

Each time the Styles Gallery becomes visible it triggers an update of each style which leads to increased CPU usage. Significant performance delay is not experienced as the update is executed in dispatcher and with delayed execution. However, a blink of the styles could be noticed.

The width of the image is inherited from the table element it is in when it doesn't have a specific width set to it. Sample HTML reproducing the problem is:

<html>
	<body>
		<table style="width: 700px;">
			<tbody>
				<tr>
					<td>
						<img src="" />
					</td>
				</tr>
			</tbody>
		</table>
	</body>
</html>

Instead, the real size of the image should be used.

Workaround: Subscribe to LoadImageFromUri and set size to the image.

            settings.LoadImageFromUrl += (s, arg) =>
                {
                    if (arg.Url != null)
                    {
                        string extension = Path.GetExtension(arg.Url);
                        Uri uri = new Uri(arg.Url, UriKind.RelativeOrAbsolute);
                        System.Net.WebClient oWebClient = new System.Net.WebClient();

                        using (MemoryStream stream = new MemoryStream())
                        {
                            oWebClient.OpenRead(uri).CopyTo(stream);
                            arg.ImageElement.Init(stream, extension);
                            arg.ImageElement.Size = new Size(164, 80);

                            e.Handled = true;
                        }
                    }
                };

RadRichTextBox/RadDocumentEditor's MailMerge(bool) method doesn't respect the startEachRecordOnNewPage parameter. When the parameter is set to 'false', records are still merged on different pages, instead of on one.

Workaround: Use RadDocumentMerger to append the resultant documents:
http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/features/merge-documents/append