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

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

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

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

The current implementation of Persist State http://demos.telerik.com/kendo-ui/grid/persist-state isn't meant to save the user state of the grid.

Let me explain.
Currently setOptions() override the options in the grid. That has a rather unfortunate side effect. The Column[{...}] options coming from the server is no longer used (ever) as all column options are now coming from the client. Effectively overriding all column options.

Example:
{
   ...,
   columns: [
      { field: "Name", filterable: false }
   ]
}

This is saved using the current persist state.
Later the backend now supports filtering of the "Name" field, and we change filterable to true. The user will not see this change. Because it's overridden with the column options stored on the client.

It would be nice if this wasn't the case.
Either make a new method get-/setUserOptions() or change the current get-/setOptions() (I cannot figure out the usecase for the current implementation as it to me always would be used for what I've described here - and do a poor job of it)

However we also need to recognize that different options have different life cycles.
For example would I want to save current page, sorting and filters in sessionStorage.
While column order, size and pageSize (don't override, just set. As the range can change) would be saved in localStorage.
So that need to be easy to do.

The last thing we need is an event where it would make sense to call setUserOptions(). For the purpose of loading saved state without having to click a "Load state" button. The event needs to be before the datasource is quried. 
The current dataBinding event doesn't work as it would result in an infinite loop of datasource queries.

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!

Hi,

Currently the Selection & Export functionality does not automatically scroll down/up the Grid when the user tries to select cells that fall out of the view. Would be great if we have an option to allow automatic scroll and provide ability to choose additional cells (as in excel). Additional details are in 1576704.

We are extensively using this selection feature and the above mentioned behavior would save lot of our time and add value to the functionality.

Appreciate your support on this.

Thanks,

Raj

We have a project where we need the infinite scroll, column sorting/filtering, and remote data enabled.  We are having some issues with sort and filter.  For quick reference, I used the grid demo and changed it to reflect our configuration.  The problem is the grid fires the read command twice when we have loaded more than one page of data. No issues when we have only loaded the first page.

https://dojo.telerik.com/UDoREFID

To reproduce:

1.  Open Chrome

2.  Load the page

3. Hit run

4. Open Developer Tool

5. Switch to the Network tab and filter by XHR only  

7. Click ProductName to sort. There is only one AJAX call.

8. Scroll to the bottom so it loads the next page. It made two AJAX calls

When a user groups by a foreignkey column, it should show and sort by the value that's displayed in that column, NOT the underlying id value.  I do have a workaround, but it seems like this is something that should be handled "out of the box".

Hi,

We have extensively used the Kendo Grid's current() function to get the current selected cell in the grid. It appears this field is always returning undefined when used in a touch enabled device (e.g. Notebooks with touch screen, Surface, Mobile Devices). We have tried this with various browsers including Chrome and Firefox. 
To reproduce the issue in Google Chrome, please follow the following steps:

Go to Developer Console
Go to Emulation Tab
Select Model: Notebook with touch 
Open the following link: http://jsbin.com/qivigoceva/1/edit?html,js,console,output
Select a cell in the grid. The console should show the reference to current cell. It will instead show undefined.

The current() function is extremely important to us as we need to get the cell reference. Currently many of our client's are having trouble due this issue. Please provide us a solution as soon as possible.

=====================================================
Hello Khalil,

This behavior is expected, as the keyboard navigation is not meant to be used on touch enabled devices, as there is no hardware keyboard present. I am afraid that currently there is no workaround for this behavior.

Regards,
Kiril Nikolov 
Telerik
=====================================================

Hello Khalil,

If you want to get the currently selected element, you can use this.select() that will return the element that is selected in the change event handler.

Regards,
Kiril Nikolov 
Telerik
=====================================================

Dear Kendo Team, 
this.select() will return the current select tr , but we need the current focused td in the selected row. We cant avoid row selection in this grid.

And also we are using devices(Laptop with touch) with keyboard (hardware) .
====================================================

Hello Khalil,

I am afraid that this is not possible on touch devices. You can submit this as a feature request on UserVoice, so that it is considered for implementation in a future release.

Regards,
Kiril Nikolov 
Telerik

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.

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

For string columns especially, the default type of filter someone would want to apply is not the first option in the list. If it's not possible to reorder the items, then it should be possible to select which item is the default. This would prevent users from having to change the filter every single time.

We have a feature where we initialize our Grids with row filters, but we don't display them right away. We show hide them with a "Show/Hide Filters" button. It would be great to save some time on initial load of the grid (our client wants the ability to display up to ~100 columns with filters, and there's a noticeable performance impact building those filter controls), and delay that time for if/when the user decides they want to actually use the filters.

On Kendo Grid, It will be nice to use a combination of Server and Client side code for pagination and sorting.

I want to limit the number of rows pulled from the server by 2000 rows. On the screen, the grid can be set to a page size of 20. If the actual rows are less than 2000, there is really no need for the grid to call the server again for paging or sorting

Based on the examples here (http://demos.telerik.com/kendo-ui/web/grid/editing-custom.html), "incell" editing allows editing a single cell at a time. The edit mode is activated upon a single click in the cell.

I would like to have a way to combine this with "cell" selectable mode, e.g. like this?
* A single click on a cell selects the cell and fires the "change" event.
* A double click on a cell activates the edit mode for the cell.

"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

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

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

Grid sorting needs to sort Enum by text, not by their numeric undelaying value. Or at least it should be an option what to sort by.