We have an image control that requires an upload to be a specific size.

Rather than making our users have to manually resize their photo to the same size every time, they have requested we resize it for them since we know the size limits (96x96).

I don't see any built-in support for this so I've tried to hack it but even that hasn't worked. The "imageEditor.executeCommand({ command: "OpenPaneImageEditorCommand" })" throws an error when being called from the ImageRendered event, and manually selecting the buttons also does not resize the image.

Link to example: https://jsfiddle.net/atz9ne6g/1/

Code from example:

$("#imageEditor").kendoImageEditor({
    width: 1000,
    height: 800,
    imageLoaded: UploadPhoto_ImageLoaded,
    imageRendered: UploadPhoto_ImageRendered
});

let imageLoaded = false;
function UploadPhoto_ImageLoaded(e) {
    imageLoaded = true;
}

function UploadPhoto_ImageRendered(e) {
    if (imageLoaded) {
        imageLoaded = false;
        //var imageEditor = e.sender;
        // TODO: Auto resize photo to 96x96 when opening popup
        //imageEditor.executeCommand({ command: "OpenPaneImageEditorCommand" });
        //imageEditor.executeCommand({ command: "ResizeImageEditorCommand" });

        $(".k-i-image-resize").click();
        $(".k-formatted-value[title='width']").val(96);
        $(".k-imageeditor-pane-confirm-button").click();
    }

Currently, an inherited DropDownList widget can only bind to another of the same type  or another vanilla DropDownList (via  alternativeNames array at kendo.all.js line 32813) 

A use case is that I originally created ParentCustomDDL and ChildCustomDDL with the intention of cascading from parent -> child. Since alternativeNames is hard-coded, I was forced to merge the code into one clumsy widget so that name matches name.

For now, kendo validator validates just HTML inputs. For simple forms this is ok, but for complex models it would be nice to have a possibility to validate the entire model before posting it (which may not be directly bound to HTML fields!)

The expected scenario looks like Asp.NET mvc validation: validate() method accepts the entire view model and returns an array of error objects which are then bound to HTML labels based on their data-* attributes.

Create a new configuration option so you can not show anything when the value for a field is "null". So, for example; a mobile listview has a new property "shownullvalues", when set to false, it will not display any text when the actual field value is not present (or null).

Hi, I am using the AJAX data source for grid which is great since I don't have to requery for filter, sort, and paging functions.  However, if the grid could use this same datasource for the filter autocomplete feature, I would greatly appreciate it because right now the grid is re-hitting the datasource for this.

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.

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

There are several undocumented methods on the data source which provide some really nice functionality. The DataSource is able to store multiple 'pages' of data in an internal collections of ranges that can be accessed and populated by the range() and prefetch() methods. It looks like this is used mostly to support virtual grid scrolling, but I have found it very useful for other applications where a data source uses server operations. This is a really great feature and I'd like to see it officially supported in the future!

There should be a way to programmatically get the selected timeslots from the scheduler. This might need to have the ability to not lose focus on blur of scheduler

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.

In lieu or as part of select-all capability:

Expose a way to retrieve the filtered set of data (or keys) in the grid and other filterable controls.

In other words, when a user has applied their own filters, there is currently no method to retrieve the filtered set across the entire dataset. That makes implementing a select-all button a bit tricky as you have to either select all on the current page (view) or the entire unfiltered dataset and then apply the filter yourself.

In Kendo Web - Mobile as ListView - search field should not be scrollable, only listings should be scrollable.

If user scrolls down couple of pages down and now he wants improvise the search, then again he has to scroll back to type in search field. If only listing scrollable then search field is always visible where user can type whenever wanted.
I dont know how this is missed in the current release. This is very basic.

We use the Kendo Grid with a DataSource connected to an OData service. We also use the OOB Kendo Grid functionality to hide columns in the UI (column.hidden = true). Through testing we found out that the Kendo grid does not use the OData option of selecting specific columns for retrieval. The grid will request all columns for a table, which leads to overhead in the amount of data sent from the server to the client. We sometimes have tables with 50 columns, for which only 10 columns are shown.

For controls like ListView (web and mobile). We have features like server filtering. I feel there should be a configuration to perform filter operation mixing both client side and server side filtering. 
Scenario 1: Lets say I have 20 results to be populated based on the filter criteria and I have 2 results already present on the client side and rest 18 are present on the server rather than fetching all 20 results from server freshly this way data transfer can be optimized up to certain extent.

Scenario 2: filtering should results based on the client side results and list out 2 results and there should be option load more from server similar to outlook mail search feature.

Expose a clean way of destroying kendoDraggable.

For instance at the moment I only want selected rows in a grid to be draggable, to when a row is selected I make it draggable, but then I need to clear all other draggables in the grid.  Can't find a clean way to do this.

I need to call .center() on a kendo window to have it centered on the page.

Position and size are already included in the configuration properties of kendo window so it would be logical to include the alignment as well.

With the kendoGrid, if no columns are specified, all columns are automatically rendered. However, dates (at least, I have not tested other non-strings) are rendered in non-human-readable form (at least if they are from SQL Server).

Since date rendering is tied to culture parameters, it would make sense to specify culture at the grid object level and have dates, currency, etc. render according to that. It would also be great to have filters setup for these different types applied to dynamic columns.

When we have a Grid with Resizable Columns we may need some of them to be non-resizable (ex. a column containing only status icons).
There are work around and customizations:

Column Resize - Min Width on Resize
http://www.telerik.com/forums/column-resize---min-width-on-resize

but I believe it will be more handy to define requested behavior as a property of the specific column (ex. in row template).

Also, for non resizable columns the user should not even take a resize handle when going on a non resizable column boundary instead of try to resize and when the user leaves the resize handle the column is bouncing back (restoring) the minimum width defined.

Regards,

Thomas

The current upload control does not allow the PUT verb. This means you cannot use it with Amazon S3 without implementing a proxy server. The problem with the proxy server approach is that it places unneeded strain on your own servers and you get charged twice for data transfer, once on the way in to the proxy server and again from the proxy server to S3.

Allow inserting a row in a grid when the filter is applied and show the newly inserted row (even if it does not match the filter criteria) until the filter is re-applied by the user. This behavior is consistent with Microsoft Excel. Can the kendo grid be modified to support this behavior?