In a navigatable grid with row selection mode, It should be possible to focus row using arrow keys (up or down) instead of space bar.

Right now when user press arrow keys, only once cell is being highlighted and focused. If user wants to highlight that row then he needs to press spacebar.

this behavior is confusing for end user.

Bug report

ColumnMenu in Grid does not hide/unhide the correct column when command column is placed first

Reproduction of the problem

1. Open the Dojo
2. Open the columnMenu for one of the columns
3. Try to select a column, for example "Unit in Stock"

Current behavior

Currently, the previous column is checked/unchecked and respectively hidden ("Unit Price")

Expected/desired behavior

The column that is selected in the columnMenu should be hidden or displayed and checked/unchecked in the columnMenu

Environment

• Kendo UI version: 2020.2.617
• Browser: [all ]

In you web site we used the Html.Kendo().Grid Helper to build our code for the grid.
When a user refresh the page we want to keep the context of the grid, meaning the same page size the same sort and the same page number.

When we build the grind using Html.Kendo().Grid Helper the only option that we can not set is the Page number (the page that is being display).

I see that using the javascript we can set the page

<script>
var dataSource = new kendo.data.DataSource({
  data: [
    { name: "Tea", category: "Beverages" },
    { name: "Coffee", category: "Beverages" },
    { name: "Ham", category: "Food" }
  ],
  // set the second page as the current page
  page: 2,
  pageSize: 2
});
dataSource.fetch(function(){
  var view = dataSource.view();
  console.log(view.length); // displays "1"
  console.log(view[0].name); // displays "Ham"
});
</script>

But why this option is not available using the MVC Helper

.DataSource(dataSource => dataSource 
.Ajax().PageSize(24) 
.ServerOperation(true) // Paging, sorting, filtering and grouping will be done client-side 
.Read(read => read.Url("/results/gethomes")) 

This will be a nice feature to have.
Thanks

When the grid is grouped, the grouping column is visible with the same values in each cell of each group. Looks weird and confusing.

How can we accomplish more efficient look and hide the grouping column?  http://demos.devexpress.com/aspxgridviewdemos/GroupingSorting/Grouping.aspx 

Reference article:
http://www.kendoui.com/forums/ui/grid/how-to-hide-the-column-the-grid-is-grouped-by-additional-grouping-questions.aspx

With a batch edit grid, it would be nice to have the ability to cancel a data operation if cells have been edited.  Currently if the user edits some cells and then does a filter or paging operation before they save their changes, there is no way to warn them and prevent the operation from taking place.  So they will lose their changes.  Ideally, I'd like to have an event that fires before the read() operation is called on the datasource which would allow the read to be cancelled.

Hi,

The Kendo UI Grid has the ability to conditionally hide/show the command columns. But in order to hide some buttons from the toolbar, you need a dataBound handler. It will be useful to hide the "Create" button from non-admins, but be able to show the PDF and Excel Export or hide the entire toolbar.

We need to display a custom content in the grouping cells (the empty leftmost indentation cells in data rows). Currently it is impossible since the cells are rendered "statically" (kendo.grid.js, line 337):

function groupCells(count) {
    return new Array(count + 1).join('<td class="k-group-cell">&nbsp;</td>');
}

Currently I insert my cell content AFTER the rows are rendered using $('.k-group-cell', row).html(...). But, you know, it is far not the best approach.

Please implement a grid option, say, groupCellTemplate:string|object – it won't be too hard. And let me know if you would like me to contribute.

<div data-role="grid"
                 data-editable="true"
                 data-toolbar="['create', 'save']"
                 data-columns="columns"
                 data-bind="source: products}"></div>


 var viewModel = kendo.observable({
products:  ...
 columns:[
        {field:"id", width:50},
        {field: "name", width:200}
         ...etc
        ]
});

Hi, Please refer to the following forum for more detail about the problem and my suggestion:
http://www.telerik.com/forums/grid-row-navigation-by-keyboard#ncKqVMBBqUe5ZymNXwpFgg

Summary: I think in Grid widget, there should be difference between selectable="cell" and selectable="row" (for keyboard Up&Down Arrow navigation). or perhaps you want to add another choice, example selectable: "row cell" (to replace the current setting for "row") and the selectable = "row", just select the row not cell and also DO NOT go to grid header!
I believe it's good that you enhance/solve this shortcoming inside the Grid design, because developer like us who has already decided row selection (selectable: "row") during design-time, it doesn't make sense that still the keyboard navigation is at the cell level, isn't it?

Thank you.

Currently you can clone the Pager to make it appear both on Top/Bottom. This should be configurable so that you can have in on top of the grid or the bottom of grid or both

Allow the use of a custom filter function for a given grid. operator could be assigned a function to perform the filtering. 
        var filter = {
            field: field,
            operator: function(row, column, filterUi) {
                var fieldValue = row[column.field];
                return matchesArbitratryCriteria(fieldValue);
            },
            value: value,
        };

Add support for canvas rendering to the grid. This will improve performance of the grid considerably.

Part of our testing we have concluded that the current kendo grid is not working well with a number higher than 1000 records as it will become very slow when the user is scrolling the data. In an attempt to fix this the virtual scrolling has been introduced but this breaks the grouping as the number of records displayed do not take into consideration if a group is collapsed or not. Therefore you may end up in a situation where you collapse a group with 100 rows and the grid will not display the next groups as they are not part of the current page (e.g page size 10);



As an example of a canvas based grid see below:
https://github.com/openfin/fin-hypergrid

Provide support for momentum scrolling in Mobile Safari for virtualization of remote data grids.

http://demos.telerik.com/kendo-ui/web/grid/virtualization-remote-data.html

Searching by date range is a very common use-case in most business applications. I need a From and To calendar controls in the row filter.

I would advise Telerik to put this functionality on the roadmap, else the row filter functionality is so restrictive as to render it useless. 

I am having to roll my own filters above the grid because of this one omission which is a real shame because the rest of the Grid functionality is so good.

(I don't want to use filters in column headers because I don't like the fact you loose visibility of what filters are on - probably the reason for the grid rows introduction)

with grouping/sorting/fixed wrapper size + prevent default select

http://www.kendoui.com/forums/ui/grid/local-virtual-scrolling---my-changes-grouping-sorting-works.aspx

My changes: 
http://oskar.doppnet.com/kendo-grid/local.html
http://oskar.doppnet.com/kendo-grid/remote.html

Bug report

When a user cancels an inline edit, hidden columns appear instead of staying hidden.

Reproduction of the problem

1. Go to this Progress Kendo UI Dojo
2. Click Edit, and cancel the edit

Expected/desired behavior

The hidden columns should remain hidden upon canceling an edited row.

Environment

• Kendo UI version: 2023.2.829
• jQuery version: All Supported Versions
• Browser: all

When using Frozen columns in the grid, the frozen column is not usable for vertical scrolling when used in a mobile application. 

This means that it is not possible to swipe up and Down on the frozen column to scroll the grid vertically. This again makes the user experience very odd (actually it feels like a bug), because it is not natural to have to use the other, none froze columns, to be able to scroll vertically.

Thanks!

Jon

Adding the same functionality as filterable.extra but in row mode. Similar to the following demo http://dojo.telerik.com/AkaYi/2.

in grid when data are grouped and the group is collapsed groupFooterTemplate data should be still visible

The grid does not resize properly when placed in css flex containers (http://www.telerik.com/forums/how-to-use-grid-in-css-flexible-box#i5x2DlCtiEyWLXLVRg5U-g)  .  Would be good if it supported css flex, and the new css grid as a bonus