We use "@progress/kendo-react-treelist": "^5.10.1" in our project. Trees are usually placed in flexible containers, and users can reduce their size to 0. At this point, we get an error when calling the tableRowsVirtualization function. I have attached a screenshot at the moment of debugging. You can see that the values of items[0] and lastItem are undefined when the container size approaches 0. I didn't prepare an example to reproduce the error, because I think it's pretty clear that an error occurs here. So the questions are: if this is a bug, is it fixed in the new versions of the package? If there is a possible error on our part or it has not been fixed in the new versions, then what should we do to solve the problem? Thanks

It would be beneficial if the ExpansionPanel had allowed adding additional header content outside of the built-in title and indicator elements

It would be great if there was a mechanism for customizing the sorting of the ExpansionPanel headers

*** Support ticket created by Telerik by Progress staff ***
*** Please follow-up with additional details, if necessary. Thank you. ***

I want to achieve an improved customization over the font styling of the title and subtitle pieces using the SCSS theme variables. We want to globalize the style changes via SCSS

We should enable the Treelist not to count items on the second level.

*** Support ticket created by Telerik by Progress staff ***
*** Please follow-up with additional details, if necessary. Thank you. ***

It would be beneficial if the Chat component had an `allowDuplicates` prop that would prevent the duplication of uploaded files.

It would be great if the MultiSelect component had a valueMap prop exposed.

We are using the DateFilter from kendo-react-data-tools to filter Odata Edm.Date fields. Neither the DateFilter nor the Edm.Date fields have a time component, but toODataString from kendo-data-query turns the DateFilter value into a DateTimeOffset e.g. YYYY-MM-DDT00:00:00.000Z.

Is it possible to get a date-only value from toODataString using DateFilter?

It would be beneficial if we had a kendoSchedulerSlotSelectable exposed similar to Angular.

It would be beneficial if the DateTimePicker had a togglebutton prop so that the button is customizable. 

In the table component, the expand (‘+’) icon still appears even when there’s no data. It would be beneficial if there was a way to hide the icon out of the box.

When a Grid column is auto-sized via double-click on the resizer, the GridColumnResizeEvent does not expose the calculated width of the column. Instead, newWidth is 0 (deprecated) and the columns entry for the target column only reflects the width before resizing. 

It would be beneficial if the auto-sized column width were exposed in the GridColumnResizeEvent (e.g., by updating newWidth or adding a new property)

It would be beneficial if there was a prop that would limit the Filter depth.

Please see the example - https://codesandbox.io/p/sandbox/silly-wind-tpfg8n

When column "Unit Price" is locked, while moving the horizontal scroll bar, the group header is sticky (expected behavior), but the group footer is not sticky (wrong behavior).

Add a prop to the MaskedTextBox that returns a clean value (without mask literals) and treats an empty mask as null or "".

This will simplify form validation and submission by eliminating the need for manual cleanup of masked values like ____-____-____-____ or 1234-5678-9012-3456

When the resizing of the Grid is enabled, the expand/collapse column is always resizable.

Currently, the KendoReact DateTimePicker supports passing a DateFormatOptions object to the format prop, but it only respects the datetime property. This prevents developers from using separate localization styles for the date and time portions (e.g., date: "medium", time: "short"), which is supported by the native Intl.DateTimeFormat and toLocaleString APIs.

It would be beneficial if the DatePicker exposed an onKeyDown evet.

It would be beneficial if we had a mechanism for customizing the Chart animations.