Nested tables inherit alignment from its parent table or table cell when importing a document from HTML, but they shouldn't.
The paragraphs are also aligned incorrectly when their parent table has its align attribute set.

Images with resolution higher than the image size currently visible in the document, are printed with low quality, as if the smaller image is scaled up.

The same is observed when an image is placed in header/footer and the document is zoomed in. Then the image should be rendered with better quality if available, but currently it isn't.

Image adorner is not properly ported and it is not supported in .Net Core.

Working with PasteOptionsPopup may cause an exception in LayoutElement.SetParent. Very difficult to reproduce, having no consistent steps. Maybe it is related to undo of paste command, but there are no other clues aside from this.

   bei Telerik.Windows.Documents.Layout.LayoutElement.SetParent(LayoutElement newParent)
   bei Telerik.Windows.Documents.Layout.LayoutBox.EnsureParent()
   bei Telerik.Windows.Documents.Layout.LayoutBox.get_Parent()
   bei Telerik.Windows.Documents.Layout.FormattingSymbolLayoutBox.get_IsEndOfCell()
   bei Telerik.Windows.Documents.Layout.FormattingSymbolLayoutBox.GetFormattingSymbolVisual()
   bei Telerik.Windows.Documents.Layout.FormattingSymbolLayoutBox.get_Text()
   bei Telerik.Windows.Documents.SpanBoxPositionHandler.get_Location()
   bei Telerik.Windows.Documents.UI.DocumentWebLayoutPresenter.GetViewPointFromDocumentPosition(DocumentPosition position)
   bei Telerik.Windows.Controls.RichTextBoxUI.PasteOptionsPopup.CalculateLocation()
   bei Telerik.Windows.Controls.RichTextBoxUI.PasteOptionsPopup.OnOwnerLayoutUpdated(Object sender, EventArgs e)
   bei System.Windows.ContextLayoutManager.fireLayoutUpdateEvent()
   bei System.Windows.ContextLayoutManager.UpdateLayout()
   bei System.Windows.UIElement.UpdateLayout()

When a floating image is moved out of the viewport it disappear and only its borders stay.

Workaround: Set padding: <telerik:RadRichTextBox LayoutMode="Flow" Padding="0 0 0 500" />

Steps to reproduce: 
1. Open RadRichTextBox application

2. Set the layout mode to Web

3. Insert an image and set its text wrapping to Square (use the context menu when you click with the right mouse button on the image)

4. Move the image in a way, part of the image will go outside of the viewport

Observe: Image disappears, only the image adorner stays. Sometimes when you insert another image after the bug has occurred, the bug can be reproduced even without step 4 from the above described.

Expected: The image shall not disappear and it shall be placed near the end of the viewport, but not outside it.

The tab stop defining respective page number alignment correlates to the cell's width where the table of contents entry is positioned.

Currently, when a user double-clicks a word in RadRichTextBox and does not release the left button, moving the cursor drags the selected word. In most word processors the same actions extend the selection. 

Note: The same applies for triple click, which selects the paragraph.

When specifying an image is wrapped Top and bottom and has a large distance from text (e.g. 500px top and 500px bottom) an exception in the arrange occurs.

Steps to reproduce:
- Select image and change its Wrapping style to Top and bottom. 
- Set values 500px for distance values

If RadRichTextBox contains a table and is placed in a window and then the window is resized horizontally, the table border are moved unexpectedly and change their place relative to the content of the documen. If the window is maximized and/or restored, some of the borders disappear.

Workaround: Execute the following code snippet in window's or RadRichTextBox' SizeChanged event handler:
if (this.MyRadRichTextBox.ActiveEditorPresenter != null)
{
    this.MyRadRichTextBox.ActiveEditorPresenter.RecreateUI();
}

When text is using fonts with defined ligatures (e.g. Calibri, Gabriola, etc.) and contains character groups with defined ligature for it, the text width is measured incorrectly (shorter that it should be). As caret and selection navigates on positions computed by this measuring system, they are not synchronized with what is shown in the UI (which correctly respects the ligatures), and there is slight offset from the real character positions and/or clipping of part of the letters at the end of the line.

Examples of such groups are (depending on the font) "tt", "ff", "ffi".

RadDocument instances leak when editing a document containing a field and header/footer. The StyleRepository holds a reference to a style's document element.

Fix available in LIB Version 2017.3.1002.

The default indentation of the list bullets is different when shown in the RadRichTextBox and when exported to HTML and shown in a web browser.
There is a screenshot attached showing how the result is rendered in a web browser.

Instead of moving to the same horizontal location in the previous line the caret moves to a location further to the left. If you move the caret with the mouse or arrow keys then the up arrow key works correctly, but if you are actively typing on the current line and hit up arrow the caret usually ends up in the wrong location.

Steps to reproduce:
1. Type line and a half of text in the editor.
2. Without using the mouse, hit the Up arrow key

Expected: The caret moves to the location directly above the current caret position (with the almost the same x-coordinate on the first line).
Actual: The caret moves to the location at the beginning of the first line.

Words separated by certain punctuation symbols are treated as single word by the "spell check as you type" real-time spell checker.

Steps to reproduce:
Case 1:
1. Type 'testt/mest'.
Expected: The two wrong words should be underlined separately
Actual: The whole text is underlined.

Case 2:
1. Type 'test/mest'.
Expected: Only the second word is underlined
Actual: The two words are underlined

Case 3:
1. Type 'testt/mest
2. Show the context menu by clicking on the second word, and choose spell checking suggestion.
3. Show the context menu by clicking again on the second word.
4. Show the context menu for the first word.
Expected: Context menu contains spell checking suggestions
Actual: Context menu doesn't contain spell checking suggestion

Case 4:
1. Type 'test'mest'.
2. Shown context menu by clicking on 'test'
Expected: Context menu contains suggestion for the whole word - 'testament'
Actual: Context menu contains suggestion for the 'mest'

Case 5:
1. Type 'test.mest'.
2. Shown context menu by clicking on 'mest'
Expected: Context menu contains suggestion for the whole word - 'testament' (this happens if the context menu is shown by clicking on the 'test')
Actual: Context menu contains suggestion for the 'mest' only. Clicking on the suggestion replaces only 'mest' with the suggestion.

Case 6: (the same as Case 2, but with non-breaking space)
1. Copy and paste this text in RadRichTextBox 'testt mest' (the white space in non-breaking space)
Expected: only the second word is underlined.
Actual: both words are underlined as one.

Case 1:
Deleting selected part from the beginning of a comment range causes the caret to appear on the next document position than the expected one.
Steps to reproduce:
- Load a document with annotation ranges
- Select from the start of the annotation ranges into the first word in the range
- Hit delete/backspace or call Delete() on the API
- The cursor will end up one position too far to the right after the content is removed

Case 2:
Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd cause caret position to jump when deleting content to the right of the Annotation Range.
Steps to reproduce:
- Open a document with Annotation Ranges where SkipPositionBefore is set to false on the AnnotationRangeEnd (the Document Protection sample in the demo app can be used)
- Move the caret to the end of the range.
- Hit the delete key
Expected: The caret remains at the end of the AnnotationRange and content to the right is deleted.
Actual: Content to the right is deleted but eventually the caret will jump to the right by one position and end up outside the Annotation Range.

Permission's range bracket disappears when it is positioned on the last line of the page.

The pgMar element might be present but the margin information might be missing as shown below:
<w:pgMar w:header="720" w:footer="720" />
At the moment this overwrites the section margin information with 0. Instead the margins should remain as is.

Fix available in LIB Version 2018.2.820.

Processing hangs on HTML import when the html file contains large base64 images. 

When cells with borders are copied from Microsoft Excel and pasted in RadRichTextBox, some of the borders are missing depending on their type - for example double borders, but also some other types.