i've tried to apply autoFitColumn method for treelist accordingly to the documentation, https://docs.telerik.com/kendo-ui/api/javascript/ui/treelist/methods/autofitcolumn#autofitcolumn , and seems it assumes only "simple" columns structure, i.e. no nested headers.

Bug report

TreeList with multi-column headers and row filtering throws an error when user tries to reorder a column.

Reproduction of the problem
Open the Dojo - https://dojo.telerik.com/aFIkOPUp/3
Try to move column "position" left or right

Current behavior
Error is thrown 

Uncaught TypeError: Cannot read properties of undefined (reading 'locked')

Expected/desired behavior

Rerdering shall be allowed

Environment

jQuery version: 3.4.1

Kendo UI version: [all]
Browser: [all ]

We are currently utilizing Telerik's Spreadsheet functionality across two different technologies:

- KendoUI for jQuery: This is being used by our FrontEnd users.
- .NET Assembly of Telerik: This is employed for backend processing and interfaces.

Both Spreadsheet implementations allow us to populate data; however, we've observed a discrepancy between the two. Specifically, there is a misalignment in the available functions, where some functions accessible in KendoUI are not available in the .NET Assembly. To address this inconsistency, we request the following enhancements:

1. Unified Function List: We would like an official list of functions that are consistently supported by both the jQuery library and the .NET assembly. Currently, the frontend offers a broader range of functions than the backend. Since our system relies on both for computations, consistency is crucial.

2. Function Usage Detection: We request an event or function in both the JS and .NET implementations that can detect the functions used within a formula. This will allow us to identify discrepancies early on.

3. Backend Validation: An event that triggers when a formula entered on the frontend is valid there but would fail on the backend due to unsupported functions would be invaluable. This will help prevent issues caused by discrepancies between the frontend and backend function implementations.

4. Enhanced Backend Functionality: We also request additional functions or exposed properties on the backend to perform similar checks as described above. This is particularly important for our customizations that allow formulas to be entered directly on the backend, bypassing the spreadsheet UI.

5. Specific Error Handling: On the backend, it would be helpful to introduce a specific error type, distinct from the generic error, that indicates a calculation failure due to an unsupported function in a formula. Currently, the generic error type could indicate multiple issues, making it difficult to diagnose the root cause.

See https://demos.telerik.com/kendo-ui/menu/scrollable

When you hover over the left or right arrow on the menu, the menu scrolls.

Our client *hates* that, and only wants the menu to scroll when you actually click on the left/right arrow.

Request:

Add an option so that we can turn OFF the scrolling on hover on the left/right scroll buttons in the menu.

Support ticket related: https://www.telerik.com/account/support-center/view-ticket/1662811

In the jquery scrollView component https://docs.telerik.com/kendo-ui/api/javascript/ui/scrollview there is no current way to enableto 'endless' or 'wrap around' option like the react component has

ref: https://www.telerik.com/kendo-react-ui/components/scrollview/endless-scrolling/

Requesting that this feature be added.

For my SPECIFIC my use case (which will probably not work for everyone), I did add a workaround for now

(not fond of it as it relies on the implementation details of the current version)

In our SCSS, I added an override to force the previous/next buttons to always be visible, even after the control hides them

...
		&.k-scrollview {

			.k-scrollview-prev, .k-scrollview-next {

				//Prevent the control from hiding these buttons when it reaches the 'end'
				//We will be using some custom logic to force the 'wrap around'
				display:flex !important; 
...

Then I subscribed click events and did some manual handling on the buttons

//After the page load & scroll view is initialized...

//note: $slides is a jquery instance that the scrollView is attached to
let scrollView = $slides.data("kendoScrollView");

let $prev = $slides.find('.k-scrollview-prev');
let $next = $slides.find('.k-scrollview-next');
$prev.on("click", function (e) {
	// NOTE: Here we are looking at an 'internal' variable, this is dependent on the version of Kendo we are using - may need to change
	// in the future
	// I figured this out by looking at the implementation in the source
	//		\src\js\kendo.scrollview.js
	let pageCount = scrollView._content.pageCount;
	let currentPage = scrollView._content.page;
	if (pageCount > 1 && currentPage === 0) {
		e.preventDefault();
		e.stopPropagation();
		scrollView.scrollTo(pageCount-1);						
	}
});

$next.on("click", function (e) {
	let pageCount = scrollView._content.pageCount;
	let currentPage = scrollView._content.page;
	if (pageCount > 1 && currentPage === pageCount - 1) {
		e.preventDefault();
		e.stopPropagation();
		scrollView.scrollTo(0);						
	}
});

I am running into an issue with allowing copy/paste of dates into the filter and cell input fields. Currently, the date fields have validation to support MM/dd/yyyy, and users of the app may be trying to copy dates in that are MM/dd/yy. I would expect Kendo to auto format the date to MM/dd/yyyy after the paste happens, or at least allow support for that, but it doesn't seem to happen.

In the cell, when putting in MM/dd/yy, a validation message appears saying the date is invalid, and there doesn't appear to be a way to override that. In the filter, when putting in MM/dd/yy and submitting the filter, it doesn't stick and completely ignores the date put in.

Steps to reproduce (filter):

1. Copy a date formatted as MM/dd/yy
2. Paste it into a date column filter
3. Attempt to apply filter
4. Notice that the filter is ignored

Steps to reproduce (cell edit):

1. Copy a date formatted as MM/dd/yy
2. Paste it into a cell datepicker field
3. Notice the validation flags it as an invalid date