Progress® Telerik® UI for WPF Feedback Portal
Recently Updated
New Items
Most Popular
Status Info
Most Popular
Request a Feature Report a Bug
Unplanned
Last Updated: 10 Jul 2025 11:13 by Swapnil
RichTextBox: RtfFormatProvider: The \page tag is not respected on import.
Created by: Swapnil
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: RtfFormatProvider: The \page tag is not respected on import.
The \page tag is not respected on import. We should insert new lien o a page break.
Unplanned
Last Updated: 16 Jul 2025 08:52 by UNAI
RichTextBox: Tables lose their preferred width after changing the field display mode to name
Created by: UNAI
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Tables lose their preferred width after changing the field display mode to name
Tables lose their preferred width after changing the field display mode to name.
Completed
Last Updated: 12 Aug 2025 10:30 by ADMIN
Release 2025.3.812 (2025 Q3)
RichTextBox: When selecting spans, some of which belong to a list, the numbering option does not allow for adding them in the existing list
Created by: Stenly
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: When selecting spans, some of which belong to a list, the numbering option does not allow for adding them in the existing list
Performing selection on spans, some of which are present in a list, does not allow for including all of them in the list. Instead, the current list will have to be removed and reapplied to all selected spans.
Unplanned
Last Updated: 17 Oct 2025 08:36 by ADMIN
RichTextBox: Bold/Italic does not work for some font styles
Created by: Swapnil
Comments: 1
Category: RichTextBox
Type: Feature Request
0
RichTextBox: Bold/Italic does not work for some font styles

Bold/Italic does not work for some font styles.

This might be a framework limitation in WPF: https://www.telerik.com/forums/some-fonts-are-not-able-to-bold-italic

Sample fonts list:

  1. Tw Cen MT Condensed Extra Bold (bold/italic)
  2. Tw Cen MT Condensed (bold/italic)
  3. Sitka Text Semibold (italic)
  4. Sitka Subheading Semibold (italic)
  5. Sitka Small Semibold (italic)
  6. Sitka Heading Semibold (italic)
  7. Sitka Display Semibold (italic)
  8. Sitka Banner Semibold (italic)
  9. Segoe UI Variable Text Semibold (italic)
  10. Segoe UI Variable Text Light (bold/italic)
  11. Segoe UI Variable Display Light (bold/italic)
  12. Segoe UI Semilight (bold/italic)
  13. Segoe UI Semibold (bold/italic)
  14. Segoe UI Light (bold/italic)
  15. Segoe UI Black (italic)
  16. Script MT Bold (bold/italic)
  17. Rockwell Condensed (bold/italic)
  18. Rockwell Extra Bold (italic)
  19. Rage Italic (bold/italic)
  20. OCR A Extended (bold/italic)
  21. Nirmala UI Semilight (bold/italic)
  22. Microsoft YaHei UI Light (bold/italic)
  23. Microsoft YaHei Light (bold/italic)
  24. Microsoft JhengHei UI Light (bold/italic)
  25. Microsoft JhengHei Light (bold/italic)
  26. Malgun Gothic Semilight (bold/italic)
  27. Leelawadee UI Semilight (bold/italic)
  28. Gloucester MT Extra Condensed (bold/italic)
  29. Gill Sans Ultra Bold Condensed (bold/italic)
  30. Gill Sans Ultra Bold (bold/italic)
  31. Gill Sans MT Ext Condensed Bold (bold/italic)
  32. Gill Sans MT Condensed (bold/italic)
  33. Franklin Gothic Medium Cond (bold/italic)
  34. Franklin Gothic Heavy (bold/italic)
  35. Franklin Gothic Medium (bold/italic)
  36. Franklin Gothic Demi (bold/italic)
  37. Franklin Gothic Demi Cond (bold/italic)
  38. Franklin Gothic Book (bold/italic)
  39. Dubai Medium (bold/italic)
  40. Dubai Light (bold/italic)
  41. Corbel Light (bold/italic)
  42. Copperplate Gothic Light (bold/italic)
  43. Copperplate Gothic Bold (bold/italic)
  44. Cooper Black (bold/italic)
  45. Cascadia Mono SemiLight (bold/italic)
  46. Cascadia Mono SemiBold (italic)
  47. Cascadia Mono Light (bold/italic)
  48. Cascadia Code SemiLight (bold/italic)
  49. Cascadia Mono ExtraLight (bold/italic)
  50. Cascadia Code SemiBold (italic)
  51. Cascadia Code Light (bold/italic)
  52. Cascadia Code ExtraLight (bold/italic)
  53. Candara Light (bold/italic)
  54. Calibri Light (bold/italic)
  55. Britannic Bold (bold/italic)
  56. Bodoni MT Condensed (bold/italic)
  57. Bodoni MT Black (italic)
  58. Bernard MT Condensed (bold/italic)
  59. Bahnschrift SemiLight Condensed (bold/italic)
  60. Bahnschrift SemiLight SemiConde (bold/italic)
  61. Bahnschrift SemiLight (bold/italic)
  62. Bahnschrift SemiBold (bold/italic)
  63. Bahnschrift SemiBold SemiConden (bold/italic)
  64. Bahnschrift SemiCondensed (bold/italic)
  65. Bahnschrift SemiBold Condensed (bold/italic)
  66. Bahnschrift Light Condensed (bold/italic)
  67. Bahnschrift Light  (bold/italic)
  68. Bahnschrift Condensed (bold/italic)
  69. Arial Rounded MT Bold (bold/italic)
  70. Arial Narrow (bold/italic)
  71. Arial Black (italic)

 

Completed
Last Updated: 11 Nov 2025 08:11 by ADMIN
Release Telerik UI for WPF 2025.4.1111 (2025 Q4)
RichTextBox: Exceptions occur on loading documents with element tags that don't have direct content but are using opening and closing tags instead of self-closing tags
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Exceptions occur on loading documents with element tags that don't have direct content but are using opening and closing tags instead of self-closing tags

The RichTextBox internal logic that imports .docx documents (DocxFormatProvider) doesn't support elements that don't need direct content, but have both start and end tags. Instead such elements should use self-closing tags. 

For example, instead of <w:vertAlign w:val="baseline"></w:vertAlign> it should be <w:vertAlign w:val="baseline"/>

When such element is read during import, issues may occur. Two main known issues here are with the w:vertAlign and Relationship tags.

Using

<w:vertAlign w:val="baseline"></w:vertAlign>

instead of

<w:vertAlign w:val="baseline"/>

throws NullReferenceException with the following stack trace:

System.NullReferenceException: 'Object reference not set to an instance of an object.'
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.OpenXmlHelper.ConvertStringToBaselineAlignment(string value) Line 168 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.SpanStyleImporter.ReadBaselineAlignment(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style style) Line 243 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.SpanStyleImporter.ReadStyle(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style style) Line 88 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.StyleDefinitionsImporter.ReadSpanStyleProperties(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style style) Line 278 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.StyleDefinitionsImporter.ReadStyle() Line 188 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.StyleDefinitionsImporter.Import() Line 67 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase importer) Line 430 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentAndRelationsFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase importer) Line 406 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.Import() Line 190 C#  
Telerik.Windows.Documents.FormatProviders.OpenXml.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.DocxFormatProvider.Import(System.IO.Stream input) Line 147 C#
Telerik.Windows.Documents.dll!Telerik.Windows.Documents.FormatProviders.DocumentFormatProviderBase.Import(byte[] input) Line 90 C#

Using

<Relationship Id="rId00004" Target="styles.xml" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/styles"></Relationship>

instead of

<Relationship Id="rId00004" Target="styles.xml" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/styles"/>

throws KeyNotFoundException with the following stack trace:

KeyNotFoundException: The given key was not present in the dictionary.
    System.ThrowHelper.ThrowKeyNotFoundException() in ThrowHelper.cs
    System.Collections.Generic.Dictionary<TKey, TValue>.this[TKey].get(TKey) in Dictionary.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.PartRelationsImporter.GetRelationByID(string) in PartRelationsImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.GetRelationByID(string) in DocxImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildSection() in MainDocumentImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildBody() in MainDocumentImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildDocument() in MainDocumentImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.Import() in MainDocumentImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase) in DocxImporter.cs
    Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentAndRelationsFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase) in DocxImporter.cs

To work this around, import the document with the WordsProcessing library. If you need to display it in RadRichTextBox, you can export it again using the WordsProcessing library. This will normalize the tags. Then import it again using the RadDocument's DocxFormatProvider.

 var dplDocxFormatProvider = new Telerik.Windows.Documents.Flow.FormatProviders.Docx.DocxFormatProvider();
 RadFlowDocument flowDocument = dplDocxFormatProvider.Import(File.ReadAllBytes("../../../test.docx"), null);

 var docBytes = dplDocxFormatProvider.Export(flowDocument, null);
 File.WriteAllBytes("../../../modified-doc.docx", docBytes);

 var rtbDocxFormatProvider= new Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.DocxFormatProvider();
 RadDocument document = rtbDocxFormatProvider.Import(File.ReadAllBytes("../../../modified-doc.docx"));

 

Unplanned
Last Updated: 14 Oct 2025 07:49 by Swapnil
RichTextBox: Exception after rapidly editing the document and then performing multiple undo operations
Created by: Swapnil
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Exception after rapidly editing the document and then performing multiple undo operations
Exception after rapidly editing the document and then performing multiple undo operations. 
Unplanned
Last Updated: 15 Oct 2025 11:25 by Martin Ivanov
RichTextBox: Allow auto update of the hyperlink navigation address when the caret leaves the text span with the address
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Feature Request
0
RichTextBox: Allow auto update of the hyperlink navigation address when the caret leaves the text span with the address
Currently, when you write down a web address (e.g. https://www.google.com) and move the caret outside of the address text (usually by pressing Space or Enter), the text is automatically wrapped in a hyperlink. Any further updates on the text won't update the underlying hyperlink address.

Add an option to auto-detect changes in the hyperlink text. This is valid only when the text matches the underlying link.
Completed
Last Updated: 11 Feb 2026 09:14 by ADMIN
Release 2026.1.211 (2026 Q1)
RichTextBox: FormatException thrown during table import from a docx document when the app culture is set to Swedish (sv-SE)
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Feature Request
0
RichTextBox: FormatException thrown during table import from a docx document when the app culture is set to Swedish (sv-SE)

FormatException is thrown during the import of a table coming from a docx document when the application culture is "sv-SE". This happens when the column width in the document is a floating point number (ex: 120.65). The Swedish culture uses "," as decimal separator and " " as the number group separator, which makes any invariant decimal value (like 120.65) invalid during standard parsing (ex: float.Parse("120.65")).

Stacktrace:

FormatException: The input string '4514.5' was not in the correct format.
at System.Single.Parse(String s)
Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.TableImporter.ImportTableGrid(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style style)  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.TableImporter.Import(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style parentStyle)  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildTable(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Parsing.Style parentStyle)  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildBody()  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.BuildDocument()  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.MainDocumentImporter.Import()Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase importer)  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.ReadXmlContentAndRelationsFromPackage(Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxPartImporterBase importer)
Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.Import.DocxImporter.Import()  Telerik.Windows.Controls.RichTextBox.dll!Telerik.Windows.Documents.FormatProviders.OpenXml.Docx.DocxFormatProvider.Import(System.IO.Stream input)

To work this around, switch to InvariantCulture during the import and return the original culture after that.

 var cultureCache = Thread.CurrentThread.CurrentCulture;
 Thread.CurrentThread.CurrentCulture = System.Globalization.CultureInfo.InvariantCulture;
 Thread.CurrentThread.CurrentUICulture = System.Globalization.CultureInfo.InvariantCulture;
 var provider= new DocxFormatProvider();
 rtb.Document = provider.Import(stream);
 Thread.CurrentThread.CurrentCulture = cultureCache;
 Thread.CurrentThread.CurrentUICulture = cultureCache;

Unplanned
Last Updated: 25 Dec 2025 13:25 by Martin Ivanov
RichTextBox: The line break symbol is treated as a text character when calculating the caret position on click at the end of the line
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: The line break symbol is treated as a text character when calculating the caret position on click at the end of the line

The line break symbol (Shift+Enter) is treated as a text character and it gets measured in the document position calculations executed when you click at the end of the document (somewhere after the line break symbol which ends the line). 

This causes two visual issues. The first one is that the caret goes after the line break symbol, which means that when ShowFormattingSymbols is False an empty space (non-existing in the document) is added at the end of the line. Even if ShowFormattingSymbols=true and the line break symbol gets display, it is not expected for ,the caret to get positioned after the symbol.

The second issues is that, when you start typing after you click at the end of the line, the caret position is corrected, but this leads to a jumps of the caret with one character to the left, which brings an unpleasant visual glitch.

To work this around, you can create a custom MouseSelectionHandler and override its RegisterDocumentMouseDown method. This will allow you to check if the caret is placed after the line break symbol and manually update the caret position if that is the case.

public class CustomMouseSelectionHandler : MouseSelectionHandler
{
    private IDocumentEditorPresenter presenter;
    private RadDocument document;

    public CustomMouseSelectionHandler(RadDocument document, IDocumentEditorPresenter presenter) 
        : base(document, presenter)
    {
        this.presenter = presenter;
        this.document = document;
    }      

    public override void RegisterDocumentMouseDown(bool ctrlPressed, bool shiftPressed, Point position, UIElement originalSource = null, SourceType source = SourceType.Mouse)
    {
        base.RegisterDocumentMouseDown(ctrlPressed, shiftPressed, position, originalSource, source);
        var box = this.document.CaretPosition.GetCurrentSpanBox();
        if (box != null && box.AssociatedSpan.Text == "¬")
        {
            document.CaretPosition.MoveToCurrentLineEnd();
        }
    }
}
To register the custom handler, use the MouseSelectionHandler property of the ActiveEditorPresenter.

 this.richTextBox.Loaded += (s, args) =>
 {
     var presenter = (DocumentPresenterBase)this.richTextBox.ActiveEditorPresenter;
     presenter.MouseSelectionHandler = new CustomMouseSelectionHandler(this.richTextBox.Document, presenter);
 };

Unplanned
Last Updated: 25 Dec 2025 16:34 by Martin Ivanov
RichTextBox: The caret is not positioned at the end of the next line when moving from longer to shorter text line using the down arrow key
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: The caret is not positioned at the end of the next line when moving from longer to shorter text line using the down arrow key
The caret position is wrong on down arrow key press when moving between two lines separated by a line break. This happens when you type longer text in the first line and then press the down arrow key to move to the next line, which is shorter. The caret should be placed at the end of the second line, but instead it is positioned few characters before the end of the line.
Unplanned
Last Updated: 25 Mar 2026 10:00 by Martin Ivanov
RichTextBox: Automatically sync the font properties of the inserted content control (Sdt tag) with the paragraph where it is inserted
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Feature Request
0
RichTextBox: Automatically sync the font properties of the inserted content control (Sdt tag) with the paragraph where it is inserted
Currently, when you insert a content control using TextProperties, CheckBoxProperties, etc., the applied font is the default one for the content controls. Instead, it should use the font of the associated span/paragraph where it was inserted. For example, if you type "Hello world" and set its font size to 36, then place the cursor between "Hello" and "world" and insert a textbox content control there, the font size of the textbox will be something like 10, instead of 36.

Synchronize the font properties and make sure that the content control uses same font as the existing paragraph/span.
Unplanned
Last Updated: 28 Apr 2026 13:02 by Martin Ivanov
RichTextBox: Add import/export support for custom SdtProperties
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Feature Request
0
RichTextBox: Add import/export support for custom SdtProperties
Currently, the SdtProperties classes (ex: DateProperties) can be extended by overriding the GetBuilder() method. This allows you to implement custom ISdtBuilder that creates the document content of the SDT form. However, the custom properties are not taken into account during import/export. Consider adding some kind of custom information about the custom SdtProperties type during export and restore it during import. Or at the least provide API (like an event or method override) that can intercept the creation of the SdtProperties during import which will allow you to replace the default SdtProperties object.
Unplanned
Last Updated: 29 Apr 2026 15:24 by Martin Ivanov
RichTextBox: Font settings are not applied for newly typed text when using the font properties dialog to change the font
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Font settings are not applied for newly typed text when using the font properties dialog to change the font
Font settings are not applied for newly typed text when using the font properties dialog to change the font.
Unplanned
Last Updated: 30 Apr 2026 20:01 by Martin Ivanov
RichTextBox: Duplicated default ListItem entry in the DropDownList content form on XAML import
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Duplicated default ListItem entry in the DropDownList content form on XAML import

When a DropDownList SDT form is saved in a XAML document and then imported with the XamlFormatProvider, an extra ListItem entry is added in the items collection of the DropDownList. The extra entry is the default "Choose an item".

To work this around, iterate all ComboBoxProperties and manually remove duplicates of the "Choose an item" entry.

var dropDownLists = radRichTextBox.Document.EnumerateChildrenOfType<SdtRangeStart>()
     .Where(x => x.SdtProperties is ComboBoxProperties)
     .Select(x => x.SdtProperties).OfType<ComboBoxProperties>();
 var defaultItemString = LocalizationManager.GetString("Documents_ContentControlsGenerator_ListItem");
 foreach (var item in dropDownLists)
 {
     if (item.Items.Count > 0 && item.Items.Any(x => x.Value != defaultItemString) && item.Items.Any(x => x.Value == defaultItemString))
     {
         var occurrence = item.Items.FirstOrDefault(x => x.Value == defaultItemString);
         while (occurrence != null)
         {
             item.Items.Remove(occurrence);
             occurrence = item.Items.FirstOrDefault(x => x.Value == defaultItemString);
         }
     }
 }

Unplanned
Last Updated: 07 May 2026 12:47 by Martin Ivanov
RichTextBox: Setting span style properties after the SdtRangeEnd (content form) doesn't actually change the span style
Created by: Martin Ivanov
Comments: 0
Category: RichTextBox
Type: Bug Report
0
RichTextBox: Setting span style properties after the SdtRangeEnd (content form) doesn't actually change the span style
Moving the caret position after the SdtRangeEnd and changing the span properties (via Style or by using the ChangeFontFamily, ChangeForeColor, etc, methods of RadDocumentEditor) doesn't change the style of the text entered after the SdtRangeEnd.
64 65 66 67 68 69
Create an account Log In
View
Type
Status
Category