When Justify text alignment is applied to a paragraph, it should not increase the space between word which are before the last tab symbol for each line.

Steps to reproduce:
- Open RadRichTextBox in Paged layout mode, default A4 section size
- Type the following text:
-- "Welcome Welcome Welcome Welcome Welcome "
-- then tab symbol
-- then "test1 test1 uncharacteristically"
- Switch paragraph alignment to Justify.

Expected: The space between 'Welcome' words remains the same in Left and Justify alignments.
Actual: The space between 'Welcome' words is increased when Justify alignment is chosen, as compared to when Left is chosen.

Paragraph spacing from table style is not exported for each paragraph inside the table. The table style defines paragraph properties which should be respected when exporting the styles to HTML.

Workaround: Apply the paragraph settings coming from the table style directly to the elements.
foreach (var table in radRichTextBox.Document.EnumerateChildrenOfType<Table>())
{
    foreach (var paragraph in table.EnumerateChildrenOfType<Paragraph>())
    {
        paragraph.LineSpacing = table.Style.ParagraphProperties.LineSpacing;
        paragraph.LineSpacingType = table.Style.ParagraphProperties.LineSpacingType;
 
        paragraph.AutomaticSpacingAfter= table.Style.ParagraphProperties.AutomaticSpacingAfter;
        paragraph.AutomaticSpacingBefore = table.Style.ParagraphProperties.AutomaticSpacingBefore;
 
        paragraph.SpacingAfter = table.Style.ParagraphProperties.SpacingAfter;
        paragraph.SpacingBefore = table.Style.ParagraphProperties.SpacingBefore;
    }
}

Handwriting keyboard allows you to enter text with a pen or other stylus. This is currently not implemented in RichTextBox and when you are using handwriting keyboard, the text is inserted more than once when the stylus is lifted while writing.

The normal hyphen should break the line and the non-breaking hyphen (inserted with: alt+0173) should not break the line

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

Please check the attached screenshot.

The bullet should be aligned next to the paragraph unless another setting is explicitly applied.

The dialogs don't have an owner, thus they behave unexpected and can be easily lost from the user and block the UI.

This applies to many of the RadWindow.Alert() invocations in the UI of RichTextBox.

When the control is used in NoXaml scenario and the required resources are merged in the resources of the Window/UserControl containing RadRichTextBox, XamlParseException is thrown at runtime with a message "Cannot find resource named 'thumbStroke'."
or
the App.Current.Resources.MergedDictionaries is cleared.

Workaround: Merge Telerik.Windows.Documents.xaml and Telerik.Windows.Controls.RichTextBoxUI.xaml in App.xaml.
or
Merge the resourced before initializing RadRichTextBox:
 App.Current.Resources.MergedDictionaries.Add(new ResourceDictionary()
            {
                Source = new Uri("/Telerik.Windows.Documents;component/Themes/Styles/ImageAdornerUIResourcesDictionary.xaml", UriKind.RelativeOrAbsolute)
            });


Fix available in R3 2017 Official Release version.

The customers need to customize the dialogs for opening and saving a file. For example, they need to set a default path or extension. With the current implementation, this can be achieved by customizing the commands. Expose an API allowing them to achieve that easily.

The "initial" CSS keyword applies the initial value of a property to an element. At this point, the result shown in RadRichTextBox can be unexpected as this value is not considered but the style evaluation falls back to the default styles defined for the control and doesn't consider the ones defined in the document style.

For example, setting background-color: initial; always results in black background.

There is a large performance hit when manipulating an area of the document with many annotation ranges in it.

Fix available in LIB Version 2018.1.326.

When the width of the tab stop is set to a negative value, an ArgumentOutOfRangeException is thrown on import. Other applications handle this case and convert the value to a positive number.

Fix is available in LIB Version 2018.1.326.

Mail merge is not working for the first record in the items source when the items source is IEnumerable with deferred execution.

Workaround: convert the collection to list.

Replacing a word with the same word but with capital letters leads to an infinite loop in the FindReplaceDialog when the search and replace values are surrounded by spaces. For example, search for " and " and replace with " AND ".

Workaround: Create a custom dialog and modify the logic for replacing text.

Available in LIB Version 2018.1.319.

Add support for FILENAME field. The field could be evaluated using the last opened/saved file name.

Description:https://support.office.com/en-us/article/field-codes-filename-field-a2946f1b-d822-47dc-ba32-4482aece26bc?ui=en-US&rs=en-US&ad=US

Add support for CREATEDATE field. The field is evaluated using the document metadata.

Description: https://support.office.com/en-us/article/field-codes-createdate-field-440080d1-2d34-494f-bdca-9d451d659d46?ui=en-US&rs=en-US&ad=US

Add support for USERNAME field. The field is evaluated using the document metadata.

Description: https://support.office.com/en-us/article/field-codes-username-field-f564f516-823f-4fb9-9da8-9b6312148053?ui=en-US&rs=en-US&ad=US

In Windows 10 1709 Falls creators update there is an upgrade to Microsoft Edge, with which the copy from edge is changed:

1) no longer it is copied in "Rich Text Format"

2) the "HTML Format" data is formatted differently than before - different line separators and the whole html is placed into a single line (unlike before).

An additional line should be inserted between the inner div and the span where the first <br> is inserted.

A specific combination of document elements causes an infinite measure loop.