RadDocument instance leaks through StylesGallery when RadDocument is set multiple times in a sequence to RadRichTextBox - for example by setting RadRichTextBox.Document property multiple times. Steps to reproduce: - Start application containing RadRichTextBox with StylesGallery - Execute this code on a button click: this.radRichTextBox.Document = new RadDocument(); this.radRichTextBox.Document = new RadDocument(); Observed: RadDocument leaks through the styles gallery. Available in LIB version: 2017.1.227
Nested tables inherit alignment from its parent table or table cell when importing a document from HTML, but they shouldn't. The paragraphs are also aligned incorrectly when their parent table has its align attribute set.
If RadRichTextBox contains a table and is placed in a window and then the window is resized horizontally, the table border are moved unexpectedly and change their place relative to the content of the documen. If the window is maximized and/or restored, some of the borders disappear. Workaround: Execute the following code snippet in window's or RadRichTextBox' SizeChanged event handler: if (this.MyRadRichTextBox.ActiveEditorPresenter != null) { this.MyRadRichTextBox.ActiveEditorPresenter.RecreateUI(); }
The tab stop defining respective page number alignment correlates to the cell's width where the table of contents entry is positioned.
Select current style (the style in the selection or under the caret) in styles gallery when selection or caret position is changed.
RadDocument instances leak when editing a document containing a field and header/footer. The StyleRepository holds a reference to a style's document element. Fix available in LIB Version 2017.3.1002.
Currently HtmlFormatProvider does not export/import tables with alignment (left, center, right).
The pgMar element might be present but the margin information might be missing as shown below: <w:pgMar w:header="720" w:footer="720" /> At the moment this overwrites the section margin information with 0. Instead the margins should remain as is. Fix available in LIB Version 2018.2.820.
When document with large images (the original image cannot fit on the page without resizing) are exported to PDF, the PDF document is visualized distorted by Adobe Reader. The issue is regression, introduced in 2017 R1 SP1. Workarounds: - Use images that can fit on the page. - Zoom RadRichTextBox to scale which allows the large images to fit fully on the page. The fix is available in LIB Version 2017.2.627.
The hyperlinks are not exported properly to DOCX, RTF and HTML format if the HTTP:// prefix is not added in the address when they were created. Steps to reproduce: 1. Open RadRichTextBox and click on Insert tab -> Hyperlink 2. In address field type: www.telerik.com 3. Export the file to DOCX, RTF or HTML format 4. Open the exported file and click on the hyperlink Observed result: The hyperlink is pointing to a local resource instead of opening the URL. As a workaround, the regex used to match a partial hyperlink could be further extended. If this regex succeeds in matching a partial hyperlink the HTTP:// prefix will be automatically added to the partial hyperlink. Here is example of how the regex should be accessed: (this.radRichTextBox.InsertHyperlinkDialog as RadInsertHyperlinkDialog).HyperlinkPattern
NullReferenceException is thrown when measuring a document with floating image as the first element on a second page. The same problem can be observed during copy/paste of content, but with slightly different call stack: System.NullReferenceException: Object reference not set to an instance of an object. at Telerik.Windows.Documents.Layout.LayoutBox.get_ValidParent() at Telerik.Windows.Documents.DocumentPosition.GetCurrentParagraphBox() at Telerik.Windows.Controls.RichTextBoxUI.RadRichTextBoxRulerController.GetCurrentParagraphBox() at Telerik.Windows.Controls.RichTextBoxUI.RadRichTextBoxRulerController.AssociatedRichTextBox_LayoutUpdated(Object sender, EventArgs e) Depending on the document structure, an InvalidOperationException with message "Removed LayoutBox should not be split. Such operation will result in invalid document structure." could be also thrown. A sample call stack is: Telerik.Windows.Documents.Layout.LayoutBox.CreateNewFragment(Telerik.Windows.Documents.Layout.LayoutBox currentLineStartNode) Telerik.Windows.Documents.Layout.TableCellLayoutBox.MeasureOverrideInternal(Telerik.Windows.Documents.Model.SizeF availableSize) Telerik.Windows.Documents.Layout.TableCellLayoutBox.Telerik.Windows.Documents.Model.IBlockContainerLayoutBox.CallMeasureOverrideInternal(Telerik.Windows.Documents.Model.SizeF availableSize) Telerik.Windows.Documents.Layout.BlockContainerLayoutHelper.CheckAllFloatingBlocksAreIncluded(Telerik.Windows.Documents.Model.SizeF availableSize) Fix available in LIB Version 2018.1.312.
Currently, when a page break is added to the document, the paragraph is not split in two. It will be better to split the paragraph and add one additional paragraph in order to achieve a more consistent look of the document when applying a style, adding one of the paragraphs to a list or having different first line/hanging indentation of the paragraphs.
While clicking to position the caret at the beginning of a paragraph, the caret is jumping to the previous document position and returning back to the desired one. Fix available in LIB Version 2017.2.627.
The parent of an already removed span cannot be found and a NullReferenceException is thrown while performing Undo. Also, multiple asserts are failing in Debug mode. The stack trace is: UnhandledException: Object reference not set to an instance of an object. UnhandledException: at Telerik.Windows.Documents.Layout.LayoutElement.SetParent(LayoutElement newParent) at Telerik.Windows.Documents.Layout.LayoutBox.EnsureParent() at Telerik.Windows.Documents.Layout.LayoutBox.get_Parent() at Telerik.Windows.Documents.Layout.LayoutBox.get_ValidParent() at Telerik.Windows.Documents.WordPositionHandler.GetParentHandler() at Telerik.Windows.Documents.DocumentPosition.GetCurrentSectionBox() at Telerik.Windows.Documents.UI.DocumentPrintLayoutPresenter.GetCurrentPage() at Telerik.Windows.Documents.UI.DocumentPrintLayoutPresenter.MeasureOverride(Size availableSize) at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
RadDocument.StreamFromUriResolving is not raised for the main document when InsertPictureField is included in header or footer.
The caret (cursor) is drawn over letters. This is unpleasant, especially with small font sizes. The issue is even more noticeable when the zoom factor is bigger than 100%. Available in LIB Version 2018.1.312.