The virtual keyboard disappears when focus cell in RadGrid with batch editing in iOS8.3. The keyboard briefly shows up and gets hidden almost immediately when trying to edit item in batch edit mode.

We recently added row group functionality to our grids and we and our users are very happy with this.

Only thing that bothers us is the drop functionality on the grouppanel. We have an wish to make the drop functionality of the grouppanel much more intuitive. Especially when the RadGrid is already grouped on multiple columns.

The marker to indicate where the user will drop an existing grouping column is shown at the begin and the end of the group column connector between groups:

Because the connector is very small it is not clear to new users where the column is dropped when it is dropped on the connector.

This case can be reproduced on the RadGrid Grouping demo on your site:
http://demos.telerik.com/aspnet-ajax/grid/examples/functionality/grouping/grouping/defaultcs.aspx

Forum reference:
http://www.telerik.com/forums/grouppanel-column-drop-and-reorder#WLzO_nt1Pk2CZYPPIITYgA

Dear Team, Please add html print button as server method with radgird. So we can get the clean html page with perfect repeated headers and footer with page nos.

The setting FilterType="CheckList" does not affect detail rows in the RadGrid.  Only "Classic" filtering is implemented for detail rows. I (and definitely users) expect the same filtering functionality on both main and detail rows.

When doing batch edits on a grid if you delete a row, the row is no longer visible in the grid but it is not actually deleted until users click the 'Save' button. This has led to some confusion for our users who delete the rows then navigate off the page w/o pressing save. They think they successfully deleted the rows but when they return to the grid the rows are still present.

We have added logic when navigating away from the page that checks and prompts users if there are unsaved batch edit changes, but in case of deleted rows, when they look at the grid, there is no indication about the deleted rows so they are unaware that the rows were not actually deleted.

We like the idea of not deleting the rows until the user presses the save button, but maybe the delete action should not remove the row from the grid and instead simply strike it out, or put a 'marked for deletion' flag or do something visual to keep the row on the grid but make it obvious that it has been marked for deletion. This way users will not be confused and will know that they must click the Save for the change to take effect.