Bug report
Grid in adaptive mode does not allow column resizing on mobile devices
Reproduction of the problem
adaptiveMode: "auto"Dojo: https://dojo.telerik.com/wrQNuNbR
Run on a mobile device and try to resize 
Environment
jQuery: 2025.2.520
Kendo UI version: 2025.2.520
Browser: [all ]
Bug report
group Grid event does not trigger when performing the grouping via the column menu.
Reproduction of the problem
Dojo example - https://dojo.telerik.com/EekHxwPJ
Environment
Kendo UI version: [all]
Browser: [all]
In a Grid with filterable set to "row" and reorderable enabled, if you type something in the filter input and try selecting the text with the mouse, the column is getting dragged.
Regression introduced with 2025.2.520
The column is being dragged, preventing you from selecting the text by dragging the mouse over it
The column shouldn't be dragged.
Currently, the Typescript definition is missing information about all the possible options of the context menu, such as contextMenu.groups,  contextMenu.close, etc.
Revise the typescript definition of the Grid context menu and add the needed options.
When a draggable column is added in the Grid with incell editing and the user tries to add a new row, the first editable cell is the second cell on the row, but not the first one. After saving, the new value is saved in the first cell.
Currently, on step two, the editable cell is the UnitPrice
After entering a value, it is saved for the ProductName column
When adding a new row, the initial editable cell should be the first cell in the row (after the draggable). The new value should be saved for the same column.
When a date is selected in the Grid and the value is cleared using the filter method, the filterMenu keeps the value of the Date fields.
The Grid is filtered and the filter is cleared correctly, but the value of the date remains in the filter menu.
When the Grid filter is cleared, the value of all inputs in the filter menu should be cleared as well.
 $('.k-filter-menu-container [data-role="datepicker"]').data('kendoDatePicker').value(null)
In a Grid where the filterable.extra is set to false, the data is not filtered correctly.
Regression introduced with 2025.2.520
The column is empty after the second filtering
The data should be filtered correctly
Calling the Grid's addRow method throws an error.
Regression introduced with version 2025.3.812
An error is thrown after adding the first row
No errors should be thrown
When the Grid has no data, a horizontal scrollbar appears.
Run the Dojo - https://dojo.telerik.com/cwVUBcpz
There is a redundant scrollbar.
When there is a record in the same Grid, the scrollbar does not appear.
There should be no scrollbar when the columns have no width set and the Grid has no data.
<style>
    .k-grid-content-expander{
      width: 98% !important
    }
  </style>
Dojo - https://dojo.telerik.com/AFvkthmc
Hi Team,
I would like to request implementing the feature to allow persistent multiple row selection with virtual scrolling. I understand at the moment it is not recommended, but I would like to see this implemented in the future.
Thanks!
When the editable option is disabled in the navigatable Grid and the user presses the 'Delete' button, the row is removed.
The row is removed, although the Grid is not editable.
The rows should not be removed in the non-editable Grid.
When a column in the Grid is configured with a group template, updating a cell doesn't update the value of the group template.
Regression introduced with 2024.1.319
The value of the group template in the Total column is not updated as per the salary column
The value of the group template in the Total column should be updated as it is calculated using the Salary column
When a Grid is set to readonly mode, but it is also navigatable, and the user clicks on a cell and presses Tab, the next cell enters editable mode.
Tab.The cell is editable.
When the Grid is in readonly mode, it should not be editable when navigating using the tab key.
When a user clicks on a locked column header (for example for sorting), the focus unexpectedly shifts to the first unlocked column instead of remaining on the clicked header.
The visual/keyboard focus immediately moves to the first unlocked column. If the user clicks the second locked column, the focus shifts to the second unlocked column.
Clicking on a locked column should retain focus on that column, not move to another grid column.
The issue is a regression starting with 2022.3.913 version
When the user enters invalid data in Grid popup edit form and presses 'Enter' the Save button becomes disabled. The button does not get enabled even after entering a valid data.
The Save button becomes disabled after a validation failure and cannot be re-enabled.
The Save button should remain enabled or re-enable automatically after validation issues are resolved.
Grid rows could not be properly selected on iPad
The rows could not be selected.
It should be possible to select a row in the Grid when it is loaded on iPad.
Used device for testing: iPad Pro iOS18.6
When backspacing input in the row filter of a navigatable Kendo UI Grid, it appears to attempt to delete a record.
Filtering is prevented and a delete confirmation dialog appears. Upon selection in the dialog, the filtering occurs.
Upon editing a Kendo UI Grid with inline editing with a hidden column, the Update/Save/Cancel buttons appear in the wrong placement.
Kendo UI version: 2025.3.812
Browser: [all ]
When using the Grid's GetSelectedData method with a selectable column, the method throws an error.
The following error message occurs:
kendo.all.js:143633  Uncaught TypeError: Cannot read properties of undefined (reading 'selectedRanges')
Kendo UI version: 2025.3.812
Browser: [all ]