Completed
Last Updated: 04 Nov 2019 11:19 by ADMIN
Release LIB 2019.3.1104 (11/04/2019)
When importing a table style, which has the w:link attribute, the style is linked with the style whose ID is the link attribute's value. However, according to the specification, If the parent style is a table style, then the link element shall be ignored. DocxFormatProvider doesn't ignore this case and links the styles which might lead to StackOverflowException during the style property value evaluation.

Workaround: Remove the Linked style from table styles:
foreach (var style in this.document.StyleRepository.Styles)
{
    if (style.StyleType == StyleType.Table)
    {
        if (style.LinkedStyleId != null)
        {
            style.LinkedStyleId = null;
        }
    }
}

Completed
Last Updated: 30 Sep 2019 10:31 by ADMIN
Release 2019.3.930 (09/30/2019)
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.
Completed
Last Updated: 11 Sep 2019 06:17 by ADMIN
Release R3 2019

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.

According to mdn:
The common use of this attribute is to define the type of stylesheet being referenced (such as text/css), but given that CSS is the only stylesheet language used on the web, not only is it possible to omit the type attribute, but is actually now recommended practice. 


Think of improving the message of the exception we throw if no data is loaded.

Workaround: set type explicitly:
<link rel="stylesheet" type="text/csshref="main.min.css" />

Completed
Last Updated: 01 Jul 2019 07:14 by ADMIN
Release LIB 2019.2.701 (07/01/2019)
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:
document.DefaultTabStopWidth = 0.1;
Completed
Last Updated: 07 Aug 2019 13:30 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
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.
Completed
Last Updated: 07 Aug 2019 13:23 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
Created by: Blane Bunderson
Comments: 0
Category: WordsProcessing
Type: Bug Report
1
Hyperlinks created via HtmlFormatProvider are not properly exported to PDF and cannot be clicked.
Completed
Last Updated: 13 Mar 2019 10:59 by ADMIN
By specification, the src attribute for images in the HTML content must be present and must contain a valid non-empty URL potentially surrounded by spaces.

However when embedded images with leading white spaces are imported, UriFormatException: 'Invalid URI: The Uri string is too long.', is thrown.
Completed
Last Updated: 26 Oct 2018 14:00 by ADMIN
ADMIN
Created by: Boby
Comments: 0
Category: WordsProcessing
Type: Bug Report
0
When the value in the document variable collection and the argument of the DOCVARIABLE fields are with different casing, the field is not updated.

Available in LIB Version 2018.3.1029.
Completed
Last Updated: 31 Jul 2019 07:13 by ADMIN
Release LIB 2019.2.805 (08/05/2019)
When the document contains an image with extension, which is not among the supported ones, a KeyNotFoundException is thrown during Import.
Completed
Last Updated: 23 Apr 2018 07:06 by ADMIN
Run's default constructor creates it with Text = null. When document with such run is exported to PDF, NullReferenceException is thrown.

Workaround: Create the Run and immediately set its Text property to string.Emtpy.

Available in LIB Version 2018.1.423.
Completed
Last Updated: 16 Oct 2018 14:19 by ADMIN
A NullReferenceException is thrown when importing a hyperlink that doesn't contain any run elements. Similar hyperlinks could be skipped so the document can be successfully imported. 

Available in R3 2018 SP1 release.
Completed
Last Updated: 14 Feb 2019 15:31 by ADMIN
When MergeField is present in the document, and this merge field is evaluated to an empty string - this, for example, happens when the property in the data source is set to null, empty string, or is missing at all - the result fragment remains in the result document. Instead, it should be removed.

Steps to reproduce: 
- Create document with merge field, the field should contain result fragment, and set data source which contains null or string.Empty value for the field:

            RadFlowDocument document = new RadFlowDocument();
            RadFlowDocumentEditor editor = new RadFlowDocumentEditor(document);

            editor.InsertField("MERGEFIELD FirstName ", "«FirstName»");

            List<Person> source = new List<Person>()
            {
                new Person() { FirstName = string.Empty }
            };

            RadFlowDocument mergedDocument = document.MailMerge(source);
Expected: The result document is empty.
Actual: The result document contains "«FirstName»" string.

Available in LIB Version 2017.3.1120.
Completed
Last Updated: 14 Dec 2017 15:49 by ADMIN
Although this is not a valid table scenario we should not throw an exception when measuring and exporting such table.

Fix available in LIB Version 2017.3.1218.
Completed
Last Updated: 06 Aug 2019 13:26 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the imported html contains an attribute of the type width="", Wordsprocessing throws ArgumentException and does not import the document. 
Completed
Last Updated: 07 Aug 2019 10:57 by ADMIN
Release LIB 2019.2.812 (08/12/2019)
When the document contains an image that is defined as an external resource but is not available in the specified location and cannot be found, a KeyNotFoundException is thrown. Handle this exception and replace the missing image with a default one for such cases. Consider exposing an option to notify the user about this error.
Completed
Last Updated: 31 Jul 2019 08:24 by ADMIN
Release LIB 2019.2.805 (08/05/2019)
Importing an image from HTML with URI as a source, which has applied only width or height and exporting it to PDF (which forces getting the image data so it can be drawn) leads to an incorrect value of 1 (a default value) for the dimension that is not specified.
Completed
Last Updated: 10 Aug 2017 11:18 by ADMIN
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.
Completed
Last Updated: 31 Jul 2017 08:48 by ADMIN
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.
Completed
Last Updated: 08 Jul 2019 10:43 by ADMIN
Release LIB 2019.2.708 (07/08/2019)
An ArgumentException is thrown when importing HTML containing standard and non-standard pseudo classes or pseudo elements. The concreete scenario is the following: 
.myclass::-webkit-scrollbar or .myclass::-ms-expand

The message of the exception is similar to this: "Unexpected character found at position [X]: ".. scrollbar::>>-<<webkit-scrollbar"". 
1 2