The delay is observed when the project already references one of our WPF NuGet and you open the NuGet window to add more NuGets.

List numbering should be restarted when copied list is pasted after content that is not in a list.

Steps to reproduce:
1. Create a file with a list, a blank line, some text, and another blank line
2. Copy the list
3. Paste it on the blank line directly after the list
Expected: The items are added to the end of the existing list
Observed: The items are added to the end of the existing list
4. Paste it on the blank line after the text
Expected: The items are added to a new list and start numbering at 1
Observed: The items are added to the existing list and start numbering at 7

Workaround:
private void RadRichTextBox_CommandExecuting(object sender, Telerik.Windows.Documents.RichTextBoxCommands.CommandExecutingEventArgs e)
{
    if (e.Command is PasteCommand)
    {
        DocumentPosition position = new DocumentPosition(this.radRichTextBox.Document);
        position.MoveToPosition(this.radRichTextBox.Document.CaretPosition);
        position.MoveUp();
        Paragraph previousParagraph = position.GetCurrentParagraphBox().AssociatedParagraph;
        if (previousParagraph.IsInList)
        {
            // We shouldn't restart the numbering when the previous paragraph is in a list.
            return;
        }

        RadDocument doc = ClipboardEx.GetDocument().ToDocument();
        Paragraph firstParagraph = doc.EnumerateChildrenOfType<Paragraph>().First();
        if (firstParagraph != null && firstParagraph.IsInList)
        {
            RadDocumentEditor editor = new RadDocumentEditor(doc);
            editor.Document.CaretPosition.MoveToStartOfDocumentElement(firstParagraph);
            editor.RestartListNumbering();
        }

        this.radRichTextBox.InsertFragment(new DocumentFragment(doc));
        e.Cancel = true;
    }
}

The WPF .NET Core 3 packages reference assemblies from SharpDX project. For one, these assemblies only work with .NET Framework 4.x. In addition, the project will not be developed further and there will not be a version compatible with .NET Core 3.x or later versions. I consider this as a serious bug and Telerik should think about removing the SharpDX assemblies and swapping it for another. Even if my project compiles without errors, you always have the warning signs on the dependencies.

When setting IsSynchronizedWithCurrentItem to true, the RadListBox behaves differently from the standard ListBox; changing the selection in the RadListBox does not update the current item of the underlying ICollectionView.

It seems that on some devices a touch with the Stylus doesn't fire the WPF native Touch events. Only the Stylus events will be fired. Because the TouchManager internally works only with the WPF Touch events, the manager's events are not fired.

When a document is imported (for example from XAML) and then exported to DOCX or RTF, the fields lose their formatting. The issue is not observed if the document is just created.

Export and then import a linked style with HtmlFormatProvider and the style gets lost on import.

When the StyleManager is applied to the control, the IsRippleEnabled property is not respected.

The event args for the RadDocking.ActivePaneChanged are named "ActivePangeChangedEventArgs" which I'm assuming is a typo for "ActivePaneChangedEventArgs".

maybe there are some ways to appear the  mouse point offset grow in steps when move the float window in raddocking by mouse drag.but I found when move the float window's header pass the document's tab,don't docking,then release mouse,and then move the float window again back and forth or up and down,the  mouse point offset grow in steps, at last the mouse's point leave the float window's header with hold the window's drag state.

When using OpenStreetMaps with APIKey (required for Cycle and Transport variations)

the key is not automatically passed to the builtin minimap and it shows 'Api Key Required' in some tiles.

The image quality is changed when pasting an image. 

We distribute two types of themes solutions with our source code. The first one are: Themes.Sources.sln (for Silverlight), Themes.Sources_WPF.sln and Themes.Sources_NetCore.sln which are used to rebuild our themes. The second one are those without Source in their names, which are used to distribute the output files. Adding references there will remove the errors which appear.