/> doesn't raise the HtmlImportSettings.LoadFromUri event on import, as we currently require type="text\css" to be specified explicitly.
typeattribute, 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:
When there is long text that is out of the used cell range area, this text should be included in page splitting calculations.
Also, when a cell has text that overflows its width, the text is again clipped by the cell boundaries and is not visible in the exported PDF. In a similar case Excel exports the surrounding cells to ensure that the content is visible.
Workaround: Extend the used cell range to include all the cells which the text content spans.
The data validation rule should have values for formula1 and formula2 elements, which define the start and end values for a range to validate between. When such values are missing, a NullReferenceException is thrown on import and the document cannot be imported.
When documents are exported to PDF, the creation date and modification date are not expected, or, when the time zone is with negative offset, the documents are invalid (detected by validation tools).
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.
The tj operator is responsible for drawing text content. When such operator is left empty, the import throws NullReferenceException because of the missing operands. Available in LIB Version 2018.3.1022.
When the string contained in a PdfHexString instance is empty, invoking ToString() leads to IndexOutOfRangeException. Available in R3 2018 SP1 release version.
This type of fields is currently not supported: https://feedback.telerik.com/Project/184/Feedback/Details/249205 . However, the fields can be skipped and the other content can be imported without throwing an exception. Fix available in R3 2018 SP1 release.