In WordsProcessing on import only the lower case CSS attributes are correctly imported. Upper case and mixed case are ignored and the default values are used.

The exception is caused by the charts import which is not implemented for WordsProcessing but the processing tries to import the charts part and process it.

An index lists the terms and topics that are discussed in a document, along with the pages that they appear on. 

HtmlFormatProvider does not maintain all the whitespaces on import even though {style="white-space: pre;"} was set.

It should support {style="white-space: pre-wrap;"} as well.

It can eventually be extended to support all the property's values: normal|nowrap|pre|pre-line|pre-wrap|initial|inherit.

The HtmlFormatProvider currently doesn't support borders for p elements.
There is a ParagraphBorders property in the model Paragraph class, but it isn't implemented in the HTML import. Also, ensure that the borders applied on div elements are preserved.

A paragraph containing multiple Hyperlinks inside Fields with missing End FieldCharacter, leads to OutOfMemoryException: 'Exception of type 'System.OutOfMemoryException' when exporting to PDF.

Workaround: Iterate all FieldCharacter instances and move any End FieldCharacter instance to paragraphs with Start FieldCharacters. See the attached project.

The mail merge should support conditional fields. Here is an example:

{ IF [Condition] [Display Result 1] [Display Result 2] }

The construct <link rel="stylesheet" href="main.min.css" /> doesn't raise the HtmlImportSettings.LoadFromUri event on import, as we currently require type="text\css" to be specified explicitly.

Provide support for Track Changes.

Such tags are not supported in RtfFormatProvider and while skipping them, there might be fields that are not properly imported. This can lead to issues while exporting the document. If the document is re-saved using MS Word, the HTML-related tags are removed and the content can be properly imported with WordsProcessing.

Create a feature that allows the RadWordsProcessing to split RadFlowDocument.

Workaround: DocumentElementImporter can be used to prepare a document element from the source document for import into the target document

RtfException "Group level reached negative value" is thrown when a document with an image defined as a resource but not found is imported and then exported to RTF

Importing document with invalid bookmarks throws System.Collections.Generic.KeyNotFoundException. The issue is caused by an invalid bookmark having missing BookmarkRangeStart/bookmarkStart or BookmarkRangeEnd/bookmarkEnd elements.

When an image is placed in a table row and the document is exported to PDF the image top edge is placed at the center of the table border because the border thickness is not respected.

The .bin extension represents a binary file format which can contain images as well. When a document containing such an image is imported and exported using WordsProcessing, the image is lost and the default 'no-image' placeholder is used in its place.

When DefaultTabStopWidth of the document is zero, the export to PDF leads to infinite loop which causes the application to freeze.

Workaround: 
Set the DefaultTabStopWidth with non-zero value:

HTML heading elements (<h1>-<h6>) are imported with the default heading styles (Heading 1 - Heading 6) for RadFlowDocument, which is unexpected, as the browsers and MS Word import them with different styling. 

"bolder" font weight is imported as regular font weight in the RadFlowDocument model. Instead, it should be imported as bold.

According to the HMTL specification, the width and height attributes of an img tag has unsigned long values. When a width or height values with a unit suffix is imported, e.g.: 50%, FormatException: 'Input string was not in a correct format.' is thrown.

Hyperlinks created via HtmlFormatProvider are not properly exported to PDF and cannot be clicked.