Any widget with the Template property should have a TemplateUrl property which allows the markup to be placed into an external html file similar to TemplateUrls in AngularJS components.

Currently, when all are enabled, it's impossible to scroll, because either multiselect starts or drag&drop. Tested on iPad OS X 11.4

Displaying multiple columns on vertical resources on kendoscheuler resources.

In some specific cases, it is required to show a bubble within a bubble in the Bubble chart. This is required to demonstrate some specific property within the bubble.
e.g.
The bubble position shows which project.
The bubble size demonstrates projects size with respect to the program.
The bubble within the bubble shows the current progress of the project.

it's looks nice if we have an option to move chatbot image to either on first or last of message for multiple messages (currently the chatbot image located on the last message)

Radio buttons fire events and web developers rely on these events to capture data or initiate a process. I fail to understand why something so basic to a control is overlooked, yet you provide this functionality to most of your other controls. 

I could attach a screen shot of this, but there doesn't seem to be a way to attach anything.

The Detailed description In:
https://github.com/telerik/kendo-ui-core/issues/3903


Bug report
Currently, DataSource bound Spreadsheet throws "Unsupported for multiple ranges" error when attempting to delete the content from multiple not adjusted cells.

The error is thrown by the values() method:

values: function (values) {
    if (this._ref instanceof UnionRef) {
        throw new Error('Unsupported for multiple ranges.');
    }
    if (this._ref === kendo.spreadsheet.NULLREF) {
....
Reproduction of the problem
Go to the DataSource Binding demo;
Select a few cells using the Ctrl + click;
Press Delete button on the keyboard;
"Unsupported for multiple ranges" error will be thrown from the values() method;

This bug has not been resolved in Version 2018.3.911. 

 I would like to see away to cross reference releases to the API docs.  So when a new method, property, etc. becomes available for a control or framework, I can see what release it was associated with.  This will permit me to upgrade apps to specific versions. Or during an update, I can see where a breaking change occurred.  I'm sure lots of other benefits could come from that.

Include Flow type definitions for kendo-ui jquery modules. 

The ImageBrowser only supports a Path and Filename to identify a file.  It would be nice to be able to use an ID instead of the Filename as an identifier.  This would involve changing the FileBrowserEntry object to include an ID property and make it available throughout (e.g. Thumbnail and Image URLs). 

As of Kendo UI R3 2018, template expressions in AngularJS are automatically escaped and as a result, our app is broken in some areas and we've rolled back to the previous version. At least give us the option to turn off escaping template expressions or offer a smarter sanitization method that can accept AngularJS template expressions within Kendo templates.

Example: https://dojo.telerik.com/uqajAsas

Check the "foo" node. The change event fires for every checked node. It would be better if it fires a single time after all nodes have been checked.

Hi,

We are using the progress functionality across the applications, also its inbuilt in Grids/Tree View or most of the Kendo controls when data is loading. Now we are hit with an Accessibility issue as stated below in JAWS 2019.

"Issue: There is a loading screen that appears throughout the application. Sighted users are able to see the loading indicator, however, screen reader users should also be aware of the loading screen."

this is what we use explicitly in some places other than the inbuilt loading indicator.

// show loading indicator
        kendo.ui.progress($("#divCriteria"), true);

So is there any settings available that we can make this screen readable when the progress bar appears? meaning if we setup globally once place it takes care across everywhere? Including Grids / Treeview etc.

I read setting this role=” aria-busy=” will do the job, but this functionality already have the kendo scripts?

<div role="alert" aria-busy="alert"> Data is loading... </div>

Appreciate a quick response or solution for this...

Thanks

Sree

In a grid with virtualization, when just normally scrolling down requests for the exact same data are often sent multiple times after each other. The reason for this is probably that the grid sends an asynchronous request for example Top 100, Skip 200 and then does not keep track of that it is still waiting for a reply for this request, before asking for the same data a short period later. 

Commonly requests for the same data is made 2 or 3 or more times after each other, causing performance problem at the server side and in many cases unnecessary calls to the database. Fixing this should lower the number of requests for data to the server considerably, maybe with a factor two or more with just normal grid operation when the user is just scrolling down to view more data in the grid.  

To demonstrate the problem, open a copy of the virtualization grid demo, for example here:

https://dojo.telerik.com/iXijoyaY

Open the Developer Tools and just observe which network requests are sent to the server. Just scroll down in any way and observe that very often the exact same request is made. A request for the same data has the same Top and Skip values in the parameters sent the server. You can see the servers reply is exactly the same JSON data multiple times after each other.

Solving this performance problem almost completely would seemingly be to in a variable just keep track of the "Latest request" sent, since the problem happens mostly just with normal scrolling in one direction with request sent after each other. So one would need to keep track of that a call for Top 100, Skip 200 has been made, and if the program wants to request the exact same data again, just wait for a reply for the first request, instead of sending a new one. (If needed, send a new request only after a specific timeout for a reply for the first one).

A more thorough solution would be to have a data structure to keep track of the Top and Skip tuples for all the calls to the server that has not yet have had a reply from the server, and not repeat those exact same calls again if still waiting for a reply for the first request.

Every time the user scrolls in a grid with virtual scrolling, the grid asks for the total number of rows satisfying the filtering conditions. This causes the same exact query to be sent to the database multiple times. Instead cache this value and only ask for it if the filters change. 

So with normal scrolling down the grid this will generate the following traffic to SQL:

Select Top 100, Skip 0 from Table where...

Select Count(*) from Table where (returns X number of rows)

Select Top 100, Skip 100 from Table  where... 

Select Count(*) from Table where (returns same X, exact same query)

Select Top 100, Skip 200 from Table  where...

Select Count(*) from Table where (returns same X)

and so on

To see this open a copy of the grid with virtual scrolling:

https://dojo.telerik.com/eDImUhOV 

Scroll the grid down:

In Developer Tools observer the result that is sent back to server includes the same:

__count: "830"

every time. In terms this will often generate a Select Count(*) being sent to the server in order to supply the answer for the current filters of the grid. An example when a Select count(*) is generated can be seen in your MVC wrappers, for example, where the toDataSourceResult() will cause this same query to repeatedly be sent to the database with every request for new data (use SQL Server Profiler or similiar to see the unnecessary queries). This is also true for your demo implemenations of the server code when used with Kendo UI.  

For grids with large data sets, as is often used with virtual scrolling, this can be a slow query. 

Instead of asking for the number of rows every time the grid is scrolled, only do so at inatialization and when the filtering conditions are changed (for example use a variable or an event to keep track of the dataSources filters changing).

If the program cannot assume that the same number of rows will be returned, then please implement a setting for developers that we can use to say that the data is not changing.

We look at historical data that are constant and with more than 100k rows, the Select count(*) puts an annecessary strain on the servers.

We could implement caching for this value, but instead the grid should not repetedly ask for the same value multiple times, instead of only when the filters change.