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
In a Grid with locked columns, there's an invalid aria-selected attribute on tr elements in the locked columns.
The tr role='none' element has invalid aria-selected attribute
The element shouldn't have the aria-selected attribute.
Reordering using clickMoveClick in the Grid is very inconsistent.
The targeted row is not being reordered
The targeted row should be reordered
I realize this has been covered by this workaround in the past, but the need to write extra code for moving the column back to the original position makes this seem a bit "hacky" and most importantly, the user experience of being allowed to drag the column in the first place just to see it jump back seems wrong.
The good news is that the kendoGrid already has a mechanism for preventing the columnReorder event from getting fired in the first place! The bad news is that it only happens for columns that have either of these 2 classes ["k-group-cell, "k-hierarchy-cell"]
My request is to have a configuration option that enforces that same behavior for specific columns as:
1. Add a "reorderable" flag to be set as part of the column configuration (set it to false for those we want to keep in place)
2. This flag will set a class on those columns the same way it works for columns with "k-group-cell" or "k-hierarchy-cell" classes, so the event can be prevented.
There is one important caveat to consider with this approach: Only columns at the front and the back of the grid can be locked in place, so there needs to be validation to prevent having non-reorderable columns among reorderable ones.
In a Grid with virtual row and column scrolling enabled, if there are large number of hidden columns, the horizontal scrolling is very slow.
Horizontal scrolling is slow
Horizontal scrolling should be smooth
In the OData v4 transport, batch submit treats a top-level HTTP 200 response as success, even when one or more operations fail. This is due to how the changesets function.
The parseBatchResponse function, which is called by the success callback belonging to the submit function of your OData v4 transport, as well as further processing in the same success callback. No attempt is made at handling anything other than responses having status codes [200... 299].
Please enhance batch handling so inner change set failures trigger explicit client error handling.
Consider the following scenario: There is a sortable Kendo-UI grid with a corresponding dataSource. Initially, the dataSource contains some items. When updating the dataSource to an empty array, all items disappear from the grid - so far, so good. However, if a column header is clicked afterwards to sort that column, the removed data reappears again.
We created a small "walkthrough" in this DOJO to demonstrate the issue.
FYI: The issue can be avoided by using a custom implementation of dataSource.transport.read which always returns the latest data.
When using the Selection and Export Grid Demo in Safari, and pasting the cells in Excel, there appears to be some extra empty lines below the paste.
The pasted lines should not include any additional empty lines beneath the specific content.
Bug report
When custom Virtual DropDownList filter is set the value is not cleared from the DropDownList on Clear button click
Reproduction
https://dojo.telerik.com/ULIgEpis
1. Filter Ship Name column
2. Open the filter menu and hit Clear
3 Open Filter menu again
Expected/desired behavior
Value shall be cleared from the DropDownList
Environment
Kendo UI version: 2021.1.301
Browser: all
When sorting is enabled for a virtualized Grid, in some cases, after scrolling to the bottom, the Grid does not show enough items to fill the tnire table.
The Grid shows only the last page of items, while there are enough items to fill up the entire table
Enough items to fill the Grid height should be displayed. There should be no blank space without records.
Bug report
Group Header appears multiple times on PDF Export if the group is separated onto multiple pages
Reproduction of the problem
Run the following Dojo:
https://dojo.telerik.com/itOpeGON/6
Click on export to PDF
Open the PDF
Scroll down until you reach Venezuela to see there are two headers for the same group
Expected/desired behavior
Only one group header shall be present at the export
Environment
Kendo UI version: all
Browser: all
Bug report
Draggable does not respect dragging object width in Grid upon dragging a column
Reproduction of the problem
Open below Dojo
https://dojo.telerik.com/iSiSeCeb
Drag Shipped Date column from the right corner
Huge gap appear between the dragged column object and the pointer
Expected/desired behavior
Pointer shall be over the dragged object
EnvironmentKendo UI version: [all]
Browser: all
When sorting is enabled for a virtualized Grid with local data, in some cases the Grid does not show correct items when sorted.
1, Open the Dojo example
2. Scroll to the bottom
3. Sort the Grid
Only the last 3 items are displayed. (screencast)
Note: The issue does not occur every time.
Enough items to fill the Grid height should be displayed. There should be no blank space without records.
When using column virtualization in Kendo Grid, the save event returns an incorrect field name. After scrolling to virtualized columns, editing a cell displays the value from a different column.
An incorrect value is displayed in the cell:
The field in the save event is not correct; instead, Field48 is logged.
The correct field should be edited and returned in the save event when editing a Grid with virtual columns.
When the Kendo UI Grid is utilizing localization with group paging, the pager does not translate.
The Pager's messages are not translated.
The Grid's pager should translate like when group paging has been disabled. (Dojo)
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 ]
The grid has a number of built in filters, what is not supported is searching for cells that have no value or some value (i.e. NULL or NOT NULL). This would be a very useful addition.
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.
Hi Team,
I would like to request a way to hide all columns with the columnMenu instead of requiring one to remain.
Thank you!
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.