The new chart select feature is great but it only works with vertically oriented charts (column), but I need it for stacked bar charts. I'd also like to be able to disable the grab handles and programatically specify the range. I have multiple similar charts, a category-specific grid with additional info, and a dropdownlist for selecting the category. You can also select the category by clicking any of the chart elements.

Add support for cell.formula on Woorbook

Notifications stack should be able to slide after previous notification hides, like in toastr:
http://codeseven.github.io/toastr/demo.html
choose Bottom Right position and add some notifications. After last hides rest slides down. Same behaviour should be possible in KendoUI Notification

Would be nice to have a validator that validates not HTML elements, but  model properties (after all when using MVVM HTML is bound to properties). Consider the following scenarios: A property is not directly bound to an HTML input. For example, I have a collection propery and my model is valid only if it contains at least N elements. Or if collection elements have date or time fields, overlaps are not allowed, and so on.

I'm writing a application and would love to have 'pull to refresh' activated when the user swipes up instead of down.  In addition, endless scrolling would work when swiping down instead of up.  Basically the reverse of how the listview works right now.  

I see this request often and users end up implementing their own solution.

The option in the Kendo Spreadsheet to show the unmarked values when a filter is applied instead to reset it by pressing the Clear button

Polymer support has already been requested but I would like to see Kendo UI support for Polymer.Dart.

Kendo OOXML should allow to give Pattern Style and Pattern Color for  cell.

It looks like this was rejected over a year ago, but now that this feature is appearing in other frameworks it would be nice to reconsider.

Each tab having its own history is core to making things work like it would in a native app. It is just so sloppy when a user loses their state going between tabs.

You are able to do this with the ionic tabtrip http://ionicframework.com/docs/api/directive/ionTab/ so i would hope kendo can too.

We have come across problems where on ann individual vie wit would be good to strip out all the CSS styling on a listview. To do this presently  is very difficult to find what styles are applied and when we do remove them it causes problems else where.
Ideally it would be nice just to have a attribute on the widget which tells the widget not to use the in built styling.

Validation errors for the bottom row of a kendo grid will be obscured behind the pager. This is a bit rubbish.

Also discussed here:

http://www.telerik.com/forums/hidden-validators-when-virtual-scrolling-createat-bottom
http://www.telerik.com/forums/the-validation-message-in-the-last-row-of-each-page-is-not-displayed

Often we want a separate delay time for the opening of menus and closing. Please consider adding independent hover delays.

$("#menu").kendoMenu({
    ...
    hoverDelay: 400
    ...
});

or

$("#menu").kendoMenu({
    ...
    hoverDelay: {
        open: 100
        , close: 500
    }
    ...
});

It would be nice to have RTL support inside Tilelayout component and fixing bug issue about RTL resizing and reordering in jquery.

Thanks.

On data management controls (like the grid and the listview), if they are bound to an ajax remote data source and an error occures, it will silently ignore it and accept the changes. You listen to the error event on the data source to display the messages, but that wont stop it from accepting the changes. You can add a single occurrence listener on the grid's data binding event to prevent it, but you are starting to get into weird hacks. Then theres the listview, which is an even uglier hack.

Not only should this be standard behavior in the first place, but it's a pain to even get it to work with hacks.

Please change the behavior or at least add an option to prevent accepting bad data that didn't even get saved in the database.

As mentioned here: http://www.telerik.com/forums/please-make-apis-used-in-your-sample-projects-official-public
you make use of kendo.date and kendo.timezone in your examples. It would be nice to know a bit more about those. And to have them available in typescript.

When multiple popovers are supported, clicking on a button to open popover1 should automatically close popover2.  Your popover demo demonstrates the problem, but bypasses the pain point by positioning the popover buttons on opposite sides of the form.  Often multiple buttons on a Nav bar will cause popovers, which will overwrite portions of each other when multiple are displayed simultaneously.  I tried a quick workaround, which didn't work.

Is there any plan to provide WEB API server wrap? If so, we can use it in web and mobile at the same time.

Now that jsbin supports Typescript, putting Kendo's typescript definitions in a public place would be helpful.  Demonstrating the power of Typescript and Kendo together in jsbin is a powerful combination for answering questions and teaching!

Add new attribute that the Validator will detect and skip validation on that element/widget.

Eg; skip-validation="true"
<input type="text" required />

and then at run time you could toggle the skip-validation attribute.

<input type="text" required skip-validation="true" />

This would be perfect for complex forms where you are togging the visibility of div container of controls depending on what options that user selects in the form. 

The problem is at the moment, the validation will validate controls that are not visible.  Having a skip-validation attribute would solve this problem, as when you hide the div container you cold also toggle the skip-validation attribute on it's input controls.

Regards,

Scott

At least, including:

1. Tab stop for mobilebutton, mobilebuttongroup, mobileswitch.
2. Selection support for mobilebutton (spacebar), mobileswitch (spacebar/left/right), mobilebuttongroup (left/right/up/down)

MobileButtonGroup and MobileSwitch are elegant replacements for radio and checkbox inputs, but they need keyboard support to improve desktop accessibility.