Add support for inline lists.
When the display attribute is set to inline all items should be on the same row (see attached)
In specific situations, a paragraph in a table cell which is last on a document page is not exported to the PDF document.
Possible workaround is adding a new paragraph to the last table cell before exporting the document.
For instance:
BlockCollection footerContent = this.document.Sections.First().Footers.Default.Blocks;
Table footerTable = footerContent.First() as Table;
footerTable.Rows.Last().Cells.First().Blocks.AddParagraph();
Support for table styles with different properties for first/last row and column, row bandings.
When the value contains a semicolon the HTML style property values are omitted on import:
<th width ='12%;' ...>
Currently, setting it without semicolon imports the value successfully:
<th width ='12%' ...>
Currently, the hyperlink is exported not as hyperlink text only but additionally, all the field data is included.
Steps to reproduce:
editor.InsertHyperlink(text:"telerik", uri:"http://www.telerik.com", isAnchor:false, toolTip:"Telerik site");
Actual: HYPERLINK "http://www.telerik.com" \o "Telerik site" Telerik
Expected: Telerik
Workaround:
IEnumerable<Run> runs = document.EnumerateChildrenOfType<Run>();
foreach (Run run in runs.ToList())
{
if (run.Text.Trim().StartsWith("HYPERLINK"))
{
run.Paragraph.Inlines.Remove(run);
}
}
From the Office Open XML specification:
gridAfter (Grid Columns After Last Cell):
This element specifies the number of grid columns in the parent table's table grid which shall be left after the last cell in the table row.
gridBefore (Grid Columns Before First Cell):
This element specifies the number of grid columns in the parent table's table grid which must be skipped before the contents of this table row (its table cells) are added to the parent table. [This property is used to specify tables whose leading edge (left for left-to-right tables, right for right-to-left tables) does not start at the first grid column (the same shared edge)]
Add support for setting and exporting document metadata, like Title, Author and similar.
Implement support for content controls (a.k.a. Structured document tags), which will allow inserting editing controls in the document: - Rich Text - Plain Text - Check Box - Combo Box - Drop-down list - Date picker Do not confuse this feature with form fields support (see https://feedback.telerik.com/Project/184/Feedback/Details/219850 ).