Undoing the action could lead to InvalidCastException, NullReferenceException, and other unexpected behaviors in next interactions with the document.

When the users didn't create a selection but rely on the caret position, the command creates selection on the current inline layout box internally. The selection's end position is on the range end, but it (the end) is not included in the actual selection. When the users try to undo, the range end is missing, which leads to incorrect visualization and different exceptions depending on the actions (when saving the document, when deleting the content, etc.).

Workaround: In CommandExecuting, check whether the selection is empty and create one if so. If the selection's end position is on an annotation range end, move the position to the next one. Clear the selection on CommandExecuted. Code is attached.

Changing the IsEnable property of the document history should clear the undo and redo. Executing undo or redo over a document with changed structure will result in an invalid document.

Steps to reproduce:
1. Add text to the RadRichTextBox.
2. Disable the document history.

Expected: The undo and redo are cleared.
Actual: the undo is not cleared and the MultipleUndoControl contains all changes.

The redo command can't be executed if a content outside of a  permission range is selected. For comparison, the undo command can be executed.

Steps to reproduce:
1. Add two paragraphs to the document with text.
2. Select the first paragraph and add permission range.
3. Protect the document.
4. Add text into the permission range.
5. Press Undo (Ctrl+Z).
6. Select text outside of the permission range.
7. Press Redo (Ctrl+R).

Expected: the redo action should be executed.

Fix available in LIB Version 2015.2.515.

The hyperlinks are not exported properly to DOCX, RTF and HTML format if the HTTP:// prefix is not added in the address when they were created.

Steps to reproduce:
1. Open RadRichTextBox and click on Insert tab -> Hyperlink
2. In address field type: www.telerik.com
3. Export the file to DOCX, RTF or HTML format
4. Open the exported file and click on the hyperlink
Observed result: The hyperlink is pointing to a local resource instead of opening the URL.

As a workaround, the regex used to match a partial hyperlink could be further extended. If this regex succeeds in matching a partial hyperlink the HTTP:// prefix will be automatically added to the partial hyperlink. Here is example of how the regex should be accessed:
(this.radRichTextBox.InsertHyperlinkDialog as RadInsertHyperlinkDialog).HyperlinkPattern

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). 

The focus stays in the combo box.

Workaround: Attach to the DropDownClosed event of the combo box and focus the presenter:
(this.radRichTextBox.ActiveEditorPresenter as Telerik.Windows.Documents.UI.DocumentWebLayoutPresenter).Focus();

Fix available in LIB Version 2017.2.522.

When document with large images (the original image cannot fit on the page without resizing) are exported to PDF, the PDF document is visualized distorted by Adobe Reader.

The issue is regression, introduced in 2017 R1 SP1.

Workarounds: 
- Use images that can fit on the page.
- Zoom RadRichTextBox to scale which allows the large images to fit fully on the page.

The fix is available in LIB Version 2017.2.627.

After further discussion within the XAML team and more research, we decided that introducing a similar property does not align with the current idea and model of RadRichTextBox. Thus, we are declining this item.

As a result RadDocument instances cannot be collected by the GC.

Some fonts doesn't include bold and italic font styles. Currently text formatted with such fonts and with applied bold or italic formatting is exported without the italic or bold effect. Instead, the default typeface can be exported, and additional transformation could be applied to the letters itself - e.g. skew transform for the italic.

When the span properties are modified (e.g. a highlight color is applied), they should not affect the span properties of the text inserted after that.

This applies for all span properties. Here are a part of them:

- Highlight color

- Foreground color

- Font weight

- Font family

- Font style

Currently, all the properties applied to the current span are inherited when the user starts typing next to it.

Implement an option for controlling how the list-style-type of a list will be exported to the HTML format.

The same issue is observed with heading styles. 
The HtmlExportSettings property PropertiesToIgnore can't be used to control how the paragraph or character properties of a list will be exported.
Steps to reproduce:
Create a document with a list of different levels.
Set fp.ExportSettings.PropertiesToIgnore["li"].Add("margin-left");
Export to HTML.
Observed: The PropertiesToIgnore doesn't work for paragraph properties of a list.

XamlParseException is thrown when importing revision date time of track changes which is exported with different than invariant culture.

Steps to reproduce: 
Set the current thread culture to "new CultureInfo("nb-NO")"
Turn on track changes.
Start the RTB and enter some text.
Export to XAML.
Import the previously exported XAML file.
Observed result:  XamlParseException is thrown when parsing the revision date time object.



Available in LIB version: 2017.1.418

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.

When the user enter text using the keyboard the PositionChanged event of the CaretPosition is not fired.
The item's status changed to Declined - the LocationChanged event can be used to track when the location of the position has been changed.

There is not defined behavior of tables without fixed column width in FlowNoWrap. They try to fill the unlimited space, so only tables with fixed width can be used in this mode. The expected behavior might be fitted column width to its content or auto fitted table width to window.

This can cause a hang of the application or unexpected behavior while working with the table (e.g. the thumbs for resizing the column width appear after the column border instead over it).

Workaround: Subscribe to CommandExecuted, get the inserted table and set a fixed width to it.

Available in R1 2018 SP2 release version.

MS Word clears the character style property of a span when a new value equal to the default value is applied. This is applicable only when the span or the parent paragraph does not have associated style which has a local property defined for the same style property.

In some cases when an image is copied from an external source and pasted in the rich text box, the image is not displayed. This is caused by the Clipboard.GetImage() method used internally by the control. 

To work this around, you can subscribe for the CommandExecuting event of RadRichTextBox and manually get the image from the clipboard.

private void Rtb_CommandExecuting(object sender, Telerik.Windows.Documents.RichTextBoxCommands.CommandExecutingEventArgs e)

{
	PasteCommand command = e.Command as PasteCommand;
	if (command != null && (Clipboard.GetData("DeviceIndependentBitmap") != null))
	{
		//Get the image stream from the clipboard.
		//You can check the following blog post for an approach which you can use to get the image properly:
		//https://www.thomaslevesque.com/2009/02/05/wpf-paste-an-image-from-the-clipboard/
		this.radRichTextBox.InsertImage(imageStream, "jpeg");
		e.Cancel = true;
	}
}	

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