Using the RadDocumentEditor class, the users can change the margin of the current section. However, there isn't a method allowing them to change the default section margin of the document. 

The event is not fired when updating the IncludePictureField fields. It is also valid when the fields are in Header or Footer. The issue is a regression in R1 2019.

The UpdateAllFields() method of RadDocumentEditor can be invoked so the event can be fired and give you the possibility to update the images.

Currently table's Rows collection only accepts adding of rows that have cells.

When RTB is placed in a ScrollViewer, typing causes invalid ScrollChanged events. They are caused by Caret's ScrollViewer, so using custom Caret and handling its ScrollChanged event should be a valid workaround.

When you first insert a table, and try to grab the right border and resize it, the result is that the inner cells resize, while the total width of the table remains the same. If you move the inner borders a bit and then try again to resize the whole table, it will work.

In MS Word, there is an option to show gridlines over the pages of the document. Implement such an option in RadRichTextBox as well.

Workaround: The attached project offers a simple custom implementation.

If you insert a picture in a RichTextBox in web layout mode and stretch it to exceed the boundaries of the control (set a smaller size to make it more convenient), a horizontal scrollbar will appear. If you do the same, but with the picture in a table, the scrollbar will not appear.

There is a NullReferenceException thrown while trying to compare positions for restoring them after pasting the document. The exception is handled but after it is thrown, the layout stops updating.

I want to import a FlowDocument into IDocumentEditor in order to obtain a RadDocument which I can convert to PDF.

Currently, the whole document is kept in memory. In some cases, this creates too much of a memory footprint (even exceeding the usable ~1.2 GB of a .NET process) and causes an OutOfMemoryException. For example, a document with around 2000 pages will fail on import. 



Optimize how style properties are used. Default style properties could be shared among all elements of the same type who does not have any local values.

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.