The TreeList renders its initial items expanded by default. However, if the Data collection is replaced, the new items will collapse.

The issue appears only when clearing the collection (or creating a new empty collection) and then adding the new items in it. If you create a new collection reference based on the current collection of items, there is no problem and the new items appear expended.

Reproduction: https://blazorrepl.telerik.com/wJEbcXvb207dv5vU11.

======

TELERIK EDIT: You can override the Equals() method of the TreeList model class to prevent the issue:

    public class Employee
    {
        public int Id { get; set; }
        public int? ParentId { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public string Position { get; set; }

        public override bool Equals(object? obj)
        {
            return obj is Employee && ((Employee)obj).Id == Id;
        }
    }

In the case of a sorted column, NVDA is not narrating the correct column name and narrating the incorrect Roles for the column headers.

In the case of an unsorted column, NVDA is narrating the column name twice and repeating the information.

After pinning an element, it goes to the side toolbar. I would like that if clicking on the name of elements in the toolbar pins them to the original position.

Description

Changing the "day" part of the DatePicker value is inconsistent.

Steps To Reproduce

Run this example: https://blazorrepl.telerik.com/QfOLwTvp03DVHJ4C35

1. Click on the "day" part of the DatePicker input and enter 22032025. The result is: 22-03-2025.
2. Click the "day" part again and enter 02.

Actual Behavior

The value changes to: 20-02-2025.

After the initial unsuccessful attempt to change the day to 02, subsequent attempts will work as expected. You may re-focus the "day" part and type 02.

Expected Behavior

The value should change to 02-03-2025.

Browser

All

Last working version of Telerik UI for Blazor (if regression)

No response

1. Activating the second tab leads to its header having the focus (correct).
2. Using the tab key, the focus changes to the second tabs content (correct).
3. Using "Shift + Tab", the focus changes back to the header row, but to the first tab header (incorrect, the second tab header should be focused).
4. Using the right arrow key, the focus changes to the third tab header and this tab gets activated (actually correct, but confusing considering the previous point).

The problem is caused by the tab index of the tab headers not being updated properly. The first one seems to have 0 at all times, while all others stay at -1. Instead, the active tab header should have tab index 0, while all others get -1.

Currently the bubble sizes in the Chart are determined automatically, according to an internal algorithm.

Please add parameters for setting specific min and max bubble sizes by the application.

When copy-pasting a cell from Excel to the Spreadsheet, our component then generates an invalid horizontal alignment value, which does not conform to the document format specification:

<alignment horizontal="start" vertical="bottom" />

The valid values for horizontal do not include start: 

<simpleType name="ST_HorizontalAlignment">
	<restriction base="xsd:string">
	<enumeration value="general"/>
	<enumeration value="left"/>
	<enumeration value="center"/>
	<enumeration value="right"/>
	<enumeration value="fill"/>
	<enumeration value="justify"/>
	<enumeration value="centerContinuous"/>
	<enumeration value="distributed"/>
	</restriction>
</simpleType>

Here are the steps:

1. Copy some basic content from Excel (two text cells)

2. Paste the content to the Telerik Blazor Spreadsheet component and save the XLSX file

Sometimes with a dropdown button I would like to have Category headers or Separators to breakup the list. To accomplish a seperator it needs to be added to another existing DropDownItem. To create a category header you can style an existing DropDownItem, however it's still clickable so it becomes obvious to the user that this is a bit of a misuse of the control. Native support for Categories or Separators would be ideal, however, just having control over the click behavior and perhaps a Template property for full control over this one items rendering would make it more extensible.

Thank you,

-Andy