It would be great if the Menu control could be auto-collapsed to fit a specified with.  If you've got more menu items than the width of your page can fit, it would be nice if the end menu items (or even menu items specified with a flag) would collapse to one nested menu item.  This should be dynamic as well.  Here is my specific example:

I've got my menu setup with controller actions attached.  Based on system permissions only the menu items the logged in user has access to will show up on the menu.  This works fine.  

A couple of the roles though have access to everything and when the menu shows all of the possible items, the menu wraps to 3 lines since it is wider than the width of my layout.  What I need is a way to auto-collapse the menu items at the end of the menu (down to one nested menu item) in the cases where it would wrap past 1 line.

Enable users of kendoCharts to show only integers on the valueAxis.

We are waiting for THE tool to help us make great animation, great binding, great web application like Silverlight to finally have application in HTML5 working on all platforms but having the tools many peoples are used to.

Good luck !

Please see 'Subject' line the <div> resizing didn't work as advertised and the splitter itself resizes to '0px'

Currently, the grid select method operates on the whole page which can easily be an issue if there is more than one HTML table.

Eg: $('#myGrid').data('kendoGrid').select('tr') should only select all rows but actually applies the 'k-state-selected' class to all <tr> elements on the page.

In cases such as $('#myGrid').data('kendoGrid').select('tr:eq(0)') may not select a row in your grid at all since it selects the first row anywhere on the.

Since I've already specified my grid by ID, I would expect the chain of functions to respect that.

Two possible workarounds are:
1. 
$('#myGrid').data('kendoGrid').select('#myGrid tr').
2. 
var grid = $("#myGrid").data("kendoGrid");
var row = grid.tbody.find("tr:eq(0)");
grid.select(row);

I use ios theme for Android to keep user interface consistent with ios and Android. However, there is a problem with form input. Please refer details in support Id: 796192. This is probably an easy fix from your guys. Thanks.

Add a "Trackball" feature in the chart for ASP.NET MVC UI (aka Kendo UI DataViz with MVC Wrappers) as described in the blogpost: http://blogs.telerik.com/iosteam/posts/14-03-04/trackball-and-annotations-for-chart-for-ios.-check.-demo-app-on-the-appstore.-check-

Hi, 
In kendo Line chart, currently the plot area can be colored using plotBands. 
In line with that is the requirement to color different ranges with different colors in the y-Axis line alone.
The line size can be made to 3 or 5 px to shown the color clearly.
This will help the user 
1. to understand the criticality of the different ranges.
2. Mostly line charts will be shown shown in reports, and will be given as printouts to the patients (in case of hospitals),  a report will have multiple line charts components, providing this feature will help the customers to reduce the cost on printer color catridges (that will be used when printing the whole plotbands for different ranges).

Thanks.

Currently when screen sizes get smaller and smaller the grid is squeezing the columns as much as possible. But if there are a lot of columns this will soon hit a size that couldn't be squeezed any more. So the result is scrolling which is giving a bad user experience. However often there are columns in a grid that could be omitted on smaller screens because they aren't that important.
How about adding some type of "class" to the grid column to tell Kendo that this column should only be shown on medium sized screens and up and another one should be shown on xs size and up (=always) and others should only be shown on large screens?

We need the ability to disable the keyboard or input read only for the combo box widget.  When we don't want a user to input their own data on the combo box currently there is no option to disable this function.

It's March 5th.  When is that Q1 release (or Beta) with the frozen / locked column feature going to be available?

I know it's still in beta, but it would be nice

The select event of the DropDownList passes an event argument e. One of the members of said argument is e.item.

Contrary to what every sane developer expects, e.item is *not* the dataItem of the datasource bound to the DropDownList, but the DOM element that represents the item visually.

The way to get to the data item is *undocumented*. Here's the necessary code:

domElem.kendoDropDownList({
    
    /*  ...  */

    select: function(e){
        var dataItem = e.sender.dataItem(e.item.index());
        // ARE YOU KIDDING ME?
    }
});


Please, PLEASE, pass the data item in the event argument.

I can't think of any case in which i would prefer the DOM element in the select handler over the data item.

Allow the user to execute certain methods of the widget and inspect the result.

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

It will be nice to have keyboard support for Grid with Virtualization of remote data (odata) and virtual scrolling enabled.

As it can depicted in your demo:
KendoUI meets Wakanda, http://wakanda.spirit.de:8081/

if you try to press key down, the grid is not scrolling down when you bypass the limit of visible rows. In addition, if you scroll down using mouse (scrollbar), if you try to press key up then the grid is not scrolling up. Also, keyboard keys page up / down, home, end and in general keyboard functionality is not supported. 

Despite of keyboard support, your demo is impressive!

Regards.

Thomas

The comboBox widget does not offer a clear (X icon) when given focus with FireFox or Chrome.  IE10 seems to work fine.  I experience this behavior on the Demo cite.

Please consider adding the onRowSelect event back to the grid so that it functions like it did in the free telerick code before Kendo. 

In Kendo If you have data and buttons (edit, destroy) on the same row: if you click one of the buttons it will act as if you clicked the data to select it.  Also, you have not provided any documentation as to how to work around this kind of problem.

When you have a ListView that can show thousands of records (presumably using a remote dataSource), it would be very useful to be able to start at a given point in the list, rather than having to start at the top of the list and scroll down thousands of records to get to the point you want.

This is currently possible to do when you have a ListView with set number of records that are all displayed at once by using the view's .scrollTo() function, but not possible when endlessScroll is on on the ListView.

Here is my original support ticket and the response I received regarding this matter:

<BEGIN MY SUPPORT TICKET>
I have a ListView which has a remote dataSource.  EndlessScroll is on in the ListView.  That part works as expected.  However, at times I need to programmatically "scrollTo" a particular point in the ListView.  To do this, I call .scrollTo() on the view's scroller (e.g. $('#MyView').data('kendoMobileView').scroller.scrollTo(0, -725)).  If I .scrollTo() a point that is too far down the page, sometimes the data doesn't show or only a couple of records/rows show and the "loading" icon is beneath them.  Here is an example of what I mean.

Given that we have a ListView with endlessScrolling on to which is attached a dataSource that reads from a remote url and has a pageSize of 50.  If we .scrollTo() about 25% down the list (approximately 13 rows down), everything works fine (i.e. after the .scrollTo() completes, we are at the row we want and all the records are there).  However, if instead of 25% we .scrollTo() about 60% down (approximately row 30), none or only some of the records with a spinning "loading" icon will be visible.

Based off of what I read here http://docs.telerik.com/kendo-ui/getting-started/mobile/listview#press-to-load-more-/-endless-scrolling, I believe what is happening is that since the ListView "adds" more of the records from the page that was retrieved from the dataSource as you scroll down the list when in virtual mode, if we .scrollTo() too far down the page, the ListView isn't smart enough to know to "add more" rows to the DOM and also make a call to the next page of the dataSource if it is necessary.  Basically, I believe ".scrollTo()" needs to trigger the ListView to add to the DOM and make a call to the next page of the dataSource the same way that scrolling with your finger would do.

I hope there is a solution/fix/hack to this because I have spent many hours on this.
<END MY SUPPORT TICKET>


<BEGIN TELERIK'S RESPONSE>
Thank you very much for the detailed information.

I am afraid that when the ListView is used in "endless scrolling" mode the scrollTo() method will not work as expected. The main idea behind the endless scrolling functionality is to load records on demand and load only the elements that the user wants to see, this is why the elements displayed are constantly changed as new items are loaded.

Currently there is not a workaround that I can offer. If you really want to see this functionality added in the future I would suggest you to check our uservoice section, where you can post this as a feature request, so it will be considered for a future implementation.
<END TELERIK'S RESPONSE>

The date/time controls in the UI for Windows suite allow you to easily select dates and times with keyboard, mouse, and touch.  By avoiding the calendar and selecting the date, month, and year separately it is quicker and easier for a user to select a date.