I would like to see the grid allow the adding of a new row via the keyboard when batch editing. When the user is on the last row and last cell they can hit tab and the grid will add a new record and with focus on the first editable cell. Or the user can hit enter anywhere on the last row to create a new row. This would allow for rapid entry of several new rows of data. It would allow the user to key in data in a similar way a spreadsheet like Excel would behave.
"NoRecordsTemplate" - At present a small text is being shown at the bottom of the grid if there are no records which is not prominent. please add back the NoRecordsTemplate so it can be displayed inside the grid and can be customized "Clear all filters" - It is very tough to clear filters one by one please all clear all option
My Kendo grid has long column titles but the column width must remain static so we need a way to make a wrapable column header
This may be more of a bug, but Kendo does not allow you to call showColumn() or hideColumn() when the grid itself is not visible. If you look in the showColumn / hideColumn methods in kendo.grid.js, we can see that there is a .filter(":visible") on the columns in place. Unfortunately for us, our Kendo grid isn't always visible (it can be collapsed: think $.slideUp). Instead, we get an error saying (on the following line) that "style" could not be set on undefined - because our hidden grid's hidden column header doesn't pass the :visible filter. Thanks!
Currently, pressing the arrow keys will scroll up and down the grid. It would be good if we could also use the arrow keys to change the selected row
would be nice to having an option to prevent specific column from re-ordering or re-sizing. In general, grid having command columns for Edit, Delete... etc buttons, these columns should not allow to reorder across columns.
Consider a grid with grouping and pagination. When we collapse a group, the items from next page should take up the space left be the hidden rows, i.e., grouping should work across pages and not just the current page. Otherwise, grouping is a useless feature in a grid with pagination. This should work for client as well as server pagination and also for virtual scroll.
there are ready to use methods fadeIn & fadeOut for animation In jQuery. Kendo UI Window already uses nifty close-effect, how about implementing this behavior for a grid-control. Expanding/Colapsing Detail-Gird in Hierarchy will go smoothly and comply with other controls' animation.
The loading indicator is not showing when the height property of a grid is not set.
I like what FooTable.js does with a html table. (hide fields based on breakpoints) and place them so that they are available via click on +
On updating the dataItem of a master row using the Observable "set()", the master row will repaint itself. However it also collapses the expanded detail row. The detail row can be expanded programmatically but this is clunky: the detail row flashes briefly while it collapses then immediately re-expands The default behaviour should be to leave the row expanded.
Enable on-the-fly changes of selectable (selection mode) in the Grid widget
Currently yo keep the selected row after refresh one needs to store the data first and then loop through all the rows to find it and select it again. This is because the uid changes after refresh. This does not work very well with large number of rows. It would be great to have a setting that allowed the selected rows or cells to be kept after the refresh.
In your article: http://www.telerik.com/forums/how-to-make-a-non-editable-column-field, many developers make the point that the read-only attribute of a column should be part of the view, not model/data. By not providing a column property to prevent editing, you have put the view logic in the wrong place. Solution: Create a read-only property to each column to prevent editing.
One should be able to cancel the detail expand or collapse events of the grids by providing a Expanding / Collapsing event. One use case for this that would be way easier to implement is when one is using a detail template to edit some form of data related to the expanded row but not bound to it's data item, instead bound to specific data coming from other source. If when you expand another row the previously expanded one gets collapsed I would like to be able to prevent that on those events to check for changes, challenge the user and act accordingly.