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.

When the main container of a window is ScrollViewer, the caret is not kept in the view while users move it with the arrow keys.

Some customers are complaining that when the mini toolbar is shown, it is semi-transparent - they expect to be fully shown. Currently, this behavior cannot be customized. Think of adding some setting about how this toolbar will be visualized.

Implement hyphenation in RadRichTextBox for different languages. 

When typing in RadRichTextBox, the characters appear in the document with slight delay.

If the font applied to text doesn't contain Bold or Italic typefaces, the text at the end of the line is clipped.

Workaround: Switch to the old rendering mode (which is somewhat slower):
this.radRichTextBox.TextRenderingMode = TextBlockRenderingMode.TextBlockWithPropertyCaching;

 ArgumentException is thrown when a missing image with no width and height is imported from HTML format.

Steps to reproduce:
1. Import the attached HTML.
2. Wait for a few second for loading the image.

Actual: An ArgumentException is thrown for setting the width or height of an image to an infinity.

Fix available in LIB Version 2017.2.522.

DocumentRuler.CreateHorizontalRuler and DocumentRulerCreateVerticalRuler properties are not always changing the visibility of the horizontal and vertical ruler when set to false. If the properties are set to false in XAML, the corresponding ruler parts are still visible.

The problem is that the values of the properties are reset internally during the controls creation, and after the layout mode of the document is changed.

Workaround: Set the properties in code behind, and reset them after layout mode change:

        public MainWindow()
        {
            InitializeComponent();

            this.ruler.CreateHorizontalRuler = false;
            this.radRichTextBox.DocumentLayoutModeChanged += (sender, e) => this.ruler.CreateHorizontalRuler = false;
        }

Bullet with a big font-size applied is not horizontally aligned with the rest of the bullets of the same level.

Steps to reproduce:
1. Add several paragraphs.
2. Apply a list to the paragraphs.
3. Select a paragraph in the middle.
5. Apply a big font-size, like 24.
6. Export to HTML.

Actual: The bullet with the bigger font-size is not horizontally aligned with the rest of the paragraphs.
Expected: All paragraphs should be horizontally aligned

A custom list applied to several paragraphs is not exported to HTML format with the required font-family and font-size.

Steps to reproduce:
1. Create a custom list with custom font-size and custom font-family. (different from the default).
2. Apply the list to several paragraphs.
3. Set the StylesExportMode property of the ExportSetting of the HtmlFormatProvider to StylesExportMode.Inline (fp.ExportSettings.StylesExportMode = StylesExportMode.Inline)
4. Export to HTML.

Actual: The bullets are exported with the default font-family Verdana and the default font-size.
Expected:  The bullets to be exported with the custom value for the font-family and font-size.

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.