We have noticed that trees with a large number of items (or deeply nested trees) consume a large amount of memory. We use external dataSources that are passed via the tree's options.

After the tree is destroyed, only a small amount of memory is freed. The rest stays allocated. Recreating the tree several times adds additional allocated memory that never becomes available again.

As far as we've seen, the dataSource itself does not offer a destroy() method or anything similar to free its resources. Is there anything we need to do to destroy the dataSource?

The Kendo UI ListView widget supports setting the selected items via the select method. Up to version 2022.2.802, calling select() triggered a change event. This is no longer the case.

You can see the different behaviors in these two DOJOS: 2022.2.802 vs 2023.1.117 (the item gets selected after a second to make sure the dataSource has finished loading).

Add a hidden input to store the current value in it at all times, and a visible display input that has the month/day/year or current value displayed in it; it solved all of the issues and is currently implemented on numerous other Kendo form input controls.

This will make the DateInput compatible with JQuery Unobtrusive Validation.