Table's layout type is imported as FixedWidth when it should be imported as AutoFit. The following RTF tags are not respected:

trftsWidthN
trwWidthBN
trftsWidthBN
trwWidthAN
trftsWidthAN
trwWidthtrftsWidthN

Add Borders property for a Run element and in CharacterProperties. The same is implemented for Paragraph, but in OOXML it could be applied over a Run element as well.

The item is duplicated. Please, follow the item at https://feedback.telerik.com/Project/184/Feedback/Details/203066

When list level items are empty - <li></li> - they are not imported as empty paragraphs in list. The expected is that a Paragraph, associated to a list to be imported.

In MS Word, decimal tab stops affect paragraph layout in table cells even if tab character is not present. The reasoning is that it's hard to insert tab symbol in table cell, as pressing Tab navigates to the next cell (Ctrl+Tab should be used). 

When decimal tab stop is present for a Paragraph, and the paragraph is in a TableCell, the content of the paragraph should be aligned to the decimal tab stop (analogically to the case when the Paragraph is not in a table cell and it contains tab character.

All character formatting (font size, font family, etc.) applied to empty cell is lost when:

- document with such formatting applied is exported to RTF

- document with such formatting is imported from RTF.

Span or paragraph style properties are not evaluated correctly when the paragraph is inside a table and there are no other local values than the one applied in the table style.

This could lead to different rendering of the document when exporting to RTF, PDF and HTML formats.

Currently empty paragraphs are exported to HTML with one space inside. Such paragraphs are not rendered by the browser. Such paragraph should be exported to HTML with one non-breaking space (@nbsp;) inside to ensure that they are visible in the browser.

Workaround: manually add nbsp-s in all empty paragraphs:
paragraph.Inlines.AddRun("\u00a0");


Steps to reproduce:
- Create document with empty paragraphs:

                        var document = new RadFlowDocument();
                        Section section = document.Sections.AddSection();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph();
                        section.Blocks.AddParagraph().Inlines.AddRun("test");

- Export it to HTML.

- Load the HTML in a browser.

Expected: The word 'test' is preceded by 3 empty rows.

Actual: The word 'test' is on the first row.

When a paragraph is placed inside a list item (<li> tag), the paragraph properties are not applied to it on import.

Add support for shapes with textual content. These are described in OpenXML specification - txbx (Textual contents of shape). 

Such shape can be added to a Word document using the Insert -> Text -> Text Box

The item is closed as duplicate. Please, follow the feature request for shapes at https://feedback.telerik.com/Project/184/Feedback/Details/190116

Updating TOC field or any other CustomCodeField that has a result fragment spread on more than one paragraph will cause an ArgumentException.

Page breaks can be exported and subsequently imported using the "page-break-before: always; " property set of some elements.

This setting should allow setting the content between the list level bullet and the paragraph text to some of the following options: "tab", "space", "nothing".

When a paragraph doesn't have applied a style, the Normal style should be automatically applied. Currently, similar paragraph obtains its style from the parent.

This is reproducible when exporting to PDF and RTF.

Workaround: Check if there is a paragraph without style ID and if so, set it to Normal:

foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    var value = paragraph.StyleId;
    if (string.IsNullOrEmpty(value))
    {
        paragraph.StyleId = "Normal";
    }
}

Available in LIB Version 2017.2.731.

The control word (\~) is imported but the symbol is not parsed, therefore not included in the content.

Fix available in LIB Version 2017.2.814.

When importing paragraphs with negative text-indent from HTML, e.g. 
<p style="text-indent:-12px;">
test
</p>

they should be imported with HangingIndent + the same value with negative sign for LeftIndent, e.g. HandingIndent: 12 AND LeftIndent: -12.

Also, margin-left should be combined with the text-indent, e.g.
<p style="margin-left: 16px;text-indent: -16px;">
test
</p>
should be imported as HandingIndent: 16 AND LeftIndent: 0.

The table height is currently not respected when applied to a table element through an attribute or through a CSS style. This setting is not respected in the flow document model, but we could import it and calculate the value to distribute it to the rows.

Currently, this property is exported only for Run and Paragraph elements.

The issue is reproducible only in a specific setup with a specific document. It is related to the calculations of the line spacing when the table row should be split between two pages.

Workaround: Change the line spacing:
foreach (var paragraph in this.document.EnumerateChildrenOfType<Paragraph>())
{
    paragraph.Properties.LineSpacingType.LocalValue = HeightType.Auto;
    paragraph.Properties.LineSpacing.LocalValue = 1;
}