1. Select all button
2. Remember selected items (now they are gone if we change page / scroll in virtual scrolling mode on)
3. Selected items count displayed on bottom bar (for example put it as neighbor of paging list)
4. Copy content of selected rows in grid (ctrl+c when selected) [data split with semicolons]
5. Export Selected/Filtered data into CVS file

Documentation on charts is very hard to navigate and search with too little examples.

put the version number on your release notes.... "Come on man"

Add documentation for each significant versions. I should not need to always update to latest Kendo UI each time I need to fix or improve something on already shipped app. I know most things are backward compatible, but keep in mind that not every time we can afford the time to update it.

Right now only words can be indented, but not Table, the format does not look tidy enough

It would be nice to have a "Show all" option on the grid, allowing to display all items on it

What a revolutionary concept, I made it myself!

would be great to have the option to set an image in a datagrids title, or alternatively be able to specify a title-template (like row-template but for headers)

Date and Time Validations & Row Selection in Grid with Checkbox to Enable Delete and Update the Selected Rows

It makes sense that grouped grids should be sorted by the group name for proper paging, however, it would be nice to be able to sort by group name THEN BY another field. Wouldn't mess up paging.

Really Meant to Say "Add a CandleStick Chart"

Elements for trivial 2 choice radio buttons like show/hide, Yes/No, etc... Of course i can use radiobuttons but for this trivial task somethong like iPhone on/off button would be more intuitive. 

At present there is no method in the grid's public API to insert an item (i.e. fully populated new row) into the grid programmatically, that is, as distinct from visual edit mode using addRow().  

There are methods to update the dataItem, and to remove an item, but no counterpart method to add an item exists. 

There are many use cases for this method; for one possible use case, please see this thread:

http://www.kendoui.com/forums/ui/grid/how-to-append-a-row-programmatically-not-in-edit-mode.aspx#2442552

For my purposes, it would be optimal if the requested addItem() method did not destroy the UI state of expanded/collapsed groups.

After it has been inserted, the item needs to behave exactly like all of the other rows in the grid: it should be "observed"; it should have a data-UID; it should have a corresponding dataItem; be included in grouping, sorting, filtering, etc etc.

we need the polymer js which is used in Kendo UI
like Angular js we need to use Polymer also

The current drop-down list works great.  However, in situations where the options are hierarchical there are (at least) two obvious solutions.

1) Have two drop-down lists (perhaps with some js altering options based on selections).

2) Display a tree of options from the drop-down. (much like a menu)

Here is an example of #1
http://www.jgeppert.com/jquery-doubleselect/


Here is a very good example of option #2
http://www.givainc.com/labs/mcdropdown_jquery_plugin.htm

The advantage to #1 is that you can easily fire off js after selected options. 

The advantage to #2 is that you can determine all available options on the server and return a structure for rendering.  Also, #2 does not take up more screen real estate. 

I think addressing these interface scenarios would help Kendo become even more usable than it already is.  

Thank you.

The ToolBar widget should provide full keyboard navigability. 
All buttons and split buttons should be accessible using the tab key.
All menu buttons should be accessible using the arrow keys when focus is on the associated split button.
Pressing the enter key should execute the buttons' associated functionality.
The toolbar's overflow menu should support keyboard navigation.

 the splash image while loading the web app initially, well, at least for the ios devices.

Routing is important for building single page apps which is missing from framework right now. 

Routing component of Backbone is very nice. Simple and intuitive. A library similar to this that is integrated into the core framework would be great.

In case there are a couple of opened modal windows(win1, win2, win3, win4) after destroying one that was closed(win5) – two next in chain(win3 and win4) becomes enabled, instead of only the last one(win4).

I’ve analyzed the code of method kendoWindow.destroy and found following lines 

if (shouldHideOverlay) {
    that._overlay(false).remove();
} else if (modalWindows.length > 0) {
    windowObject(modalWindows.eq(modalWindows.length - 2), that.options.name)._overlay(true);                 
}

It seems that line 
modalWindows.length - 2 
should be changed to
modalWindows.length - 1
as modalWindows holds currenlty opened windows, and overlay should be turned on for the last one.