When a DOCX document contains a table with fixed layout, and the table contains <tblGrid> element with improper widths (not coinciding with the ones visualized by MS Word), and such document is imported, the table is laid out with the width of the sum of the column widths imported from the table grid (tblGrid), instead of ones that could be correctly computed by the preferred width of the table cells. 



MS Word, for example, may ignore the widths specified in the tblGrid and compute new ones.



As a side effect, fixed-width tables can be laid out longer than their preferred width.

When the MoveToDocumentElementStart is called with parameter that is PermissionRangeStart and then is called a second time, the position moves to the previous position instead.

The issue is related to specific steps and is a regression released in R3 2018.

Steps to reproduce:
1. Run RadRichTextBox and insert "test" at the beginning of the document.
2. Move the caret after the 'e'
3. Press Shift+Enter to insert a line break

Observed: NullReferenceException is thrown and the UI becomes unresponsive.
Expected: The break should be successfully inserted in the content

Currently, span elements can only have highlight color and paragraphs can have a background(shading). In MS Word it is possible to apply a background to spans. The import of such a document removes the formatting.

When the user copy-pastes an image from Outlook, it is pasted as an IncludePictureField and visualized as expected. The field code looks like

{INCLUDEPICTURE :image001.png@01D15D16.4FAF0970 \* MERGEFORMATINET}

However, when the fields in the document are updated, the image is no longer shown because of its invalid Uri. In MS Word, when you paste the image, it is directly inserted as image and the field is skipped.

Workaround - remove the field start/ends (in the attachments)

Add support for positioning floating images relative to section columns. Currently, such images are laid out relative to the first column.

The customers need to additionally process the elements after inserting them into the document or just change the caret position relative to the inserted element. At this point, the methods only insert elements without returning the concrete instance or copy the element passed as a parameter, if such overload is available (editor.InsertTable(table) clones the table and inserts a different instance in the document).

 

First Scenario: During layout of specific documents where the first section is with Continuous section break type, the layout algorithm enters in an infinite loop causing the application to hang.

Workaround: Change the section break type for the first section after the import of the document and before the layout:

Second Scenario: During the layout of specific documents where the last section is with Continuous section break type and has specific page size width and height, the layout algorithm enters in an infinite loop causing the application to hang.

Workaround 2: Slightly modify the size of the section which causes the issue after the import of the document and before the layout:

Third Scenario: During layouting of specific documents containing anchored elements, the layout algorithm enters in an infinite loop causing the application to hang. No workaround.

According to the RTF Specification, each bookmark start should have a matching bookmark end. However, when opening a document which contains bookmark start without bookmark end, MS Word treats the start position for an end as well and successfully opens the document. When such document is being imported in RadRichTextBox, an InvalidCastException is thrown.

In MS Word, the users can add a source for the mail merge operation using the Select Recipients option. In the menu, they can import a file containing the data. Expose a similar option in RadRichTextBox as well.

The text-decoration-line CSS property is not imported because of wrong name definition in the parsing logic of HtmlFormatProvider.

The bolder keyword is currently not supported. In the CSS, setting bolder means one font weight heavier than the parent element, so if the parent is with font-weight, font-weight: bolder would mean that the content should be with normal font weight. In MS Word, this value is imported as bold no matter of the parent's value.

When the document is protected, RadRichTextBox.CommandExecuting is not raised when the user double clicks the header or footer area.

When custom annotations are created by inheriting AnnotationRangeStart and AnnotationRangeEnd classes, and the reaction to the delete commands is customized by overriding the DeleteBehavior, BackspaceBehavior, and DeleteSelectedBehavior, the delete command doesn't work as expected in some cases.

Some of the formatting symbols (e.g. space, tab) don't affect the height of the paragraph. With the current implementation, changing the font size of a formatting symbol, which is first in the paragraph, changes its height as well.

The issue is a regression introduced with another fix, released in R2 2018.

The properties applied locally to the content are not preserved and used for the new content when the user changes the paragraph indent.

Workaround: Keep the properties in a variable and apply them after executing the command:

StyleDefinition style;

private void RadRichTextBox_CommandExecuted(object sender, CommandExecutedEventArgs e)
{
    if (e.Command is IncrementParagraphLeftIndentCommand)
    {
        this.radRichTextBox.CurrentEditingStyle.CopyPropertiesFrom(style);
    }
}
        
private void RadRichTextBox_CommandExecuting(object sender, Telerik.Windows.Documents.RichTextBoxCommands.CommandExecutingEventArgs e)
{
    if (e.Command is IncrementParagraphLeftIndentCommand)
    {
        style = new StyleDefinition(this.radRichTextBox.CurrentEditingStyle);
    }
}

Implement import and export of OpenDocument files (.odt).

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.

When a new document is created and GetStatisticsInfo is called on it, a NullReferenceException is thrown.