Hi Team,

Background

Kendo controls column width exclusively via <colgroup><col width="Npx"> attributes. CSS min-width on <col> is not supported by browsers (per spec). There is no minWidth property in the column configuration API. When a column has no explicit width set, it can collapse to near-zero width when the grid container is narrow - making content completely unreadable. This request excludes the columns.minResizableWidth as resizable is necessary with this configuration.

Request

We need the following to work generically across all grids without per-instance config changes:

1. Column minWidth API

columns: [
  { field: "name", title: "Name", minWidth: 150 }  // ← requested or it would be great if this min width we can apply at global level
]

Where minWidth is respected even if no width is specified, and is not overridden if an explicit width larger than minWidth is set else the global min width of 150px should be considered.

2. Grid-level minWidth config

$("#grid").kendoGrid({
  minWidth: 1000  // ← requested: grid never renders narrower than this or columnCount * default columns global width (150px) whichever is higher
});

Or ideally computed automatically as Math.max(1000, columns.length * defaultMinColWidth).

Hi Team,

I would like to request a way to prevent a responsive Grid from displaying an input when the screensize/container is shorter.  Perhaps, decreasing the buttonCount automatically instead of displaying the input may be a reasonable alternative.  This would be better than setting the pageable.responsive configuration to false.  

Thank you!

Bug Report

When a navigatable Kendo UI Grid is configured with a stacked dataLayoutMode and is in an inline edit mode, using the arrow keys fails to operate as expected for the editor.

Reproducible

1. Go to this Progress Kendo UI Dojo.
2. Edit any line and get into text field or numeric field.
3. Use the arrow keys to edit the component, such as up/down for numeric change or left/right to move cursor in textbox

Current Behavior

The left and right arrow keys do not appear to function. The up and down arrows move to the next rows.

Environment

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

Hi Team,

What we're looking to achieve, is that when the page/grid enters edit mode, ALL fields in the grid should immediately become editable fields. This would help prevent the user from having to click on every cell to edit first, and the user would have a direct view of all fields actually being editable, make their changes, hit the save button on the page, and save everything at once.

Currently it's difficult for the user to actually know which fields they can edit, as they have to click a cell before it becomes editable.

Thank you!

Bug report

Reproduction of the problem

1. Open the Dojo linked here - https://dojo.telerik.com/oJOxqTQk
2. Run the page and inspect the browser console during widget initialization.

Current behavior

Initializing a hidden-by-default Kendo Grid configured with stacked layout throws a JavaScript error during initialization - Uncaught TypeError: Cannot read properties of undefined (reading 'find')

Expected/desired behavior

No errors should be thrown when initializing a hidden stacked layout Grid.

Environment

• Kendo/Telerik version: 2025.4.1321
• Browser: [all]

Hello,

We would like to request this feature to expand on a Grid components Options.

Provide a built-in way for end-users to redefine or rename a Grid column's title directly through the user interface. Currently, if a user wants to change a column header from "Title1" to "Title2”, developers must write significant custom jQuery to modify the DOM or update the column via set options.

This is a functional request from our users, that we would like to provide for them.

Thanks,
John

Hi Team,

I would like to ask for a built-in Kendo UI implementation to import Excel files into the Kendo UI Grid.  

Thank you!

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.

Bug report

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.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/XZAkgwxd
2. Scroll to the bottom and sort the table, for example, by ID

Current behavior

The Grid shows only the last page of items, while there are enough items to fill up the entire table

Expected/desired behavior

Enough items to fill the Grid height should be displayed. There should be no blank space without records.

Environment

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

Bug report

When the Kendo UI Grid is utilizing localization with group paging, the pager does not translate.

Reproduction of the problem

1. Go to this Progress Kendo UI Dojo.

Current behavior

The Pager's messages are not translated.

Expected/desired behavior

The Grid's pager should translate like when group paging has been disabled. (Dojo)

The issue is a regression starting with 2025.4.1111 version.

Environment

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

Bug report

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.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/ulIlbauD
2. Scroll and edit one of the columns, for example, edit a cell in column 'Field50'.
3. Edit the value and click outside the cell to save

Current behavior

An incorrect value is displayed in the cell:

The field in the save event is not correct; instead, Field48 is logged.

Expected/desired behavior

The correct field should be edited and returned in the save event when editing a Grid with virtual columns.

Environment

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

Hi Team,

I would like to request a way to hide all columns with the columnMenu instead of requiring one to remain. 

Thank you!

Bug report

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.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/qeSqICRA
2. Click on the 'Add' button in the toolbar to add a new row.
3. Add a value and save

Current behavior

Currently, on step two, the editable cell is the UnitPrice

After entering a value, it is saved for the ProductName column

Expected/desired behavior

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.

The issue is a regression starting with 2025.3.812

Environment

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

Bug report

When the Grid has no data, a horizontal scrollbar appears.

Reproduction of the problem

Run the Dojo - https://dojo.telerik.com/cwVUBcpz

Current behavior

There is a redundant scrollbar.
When there is a record in the same Grid, the scrollbar does not appear.

Expected/desired behavior

There should be no scrollbar when the columns have no width set and the Grid has no data.

Workaround

<style>
    .k-grid-content-expander{
      width: 98% !important
    }
  </style>

Dojo - https://dojo.telerik.com/AFvkthmc

Environment

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

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!

Bug report

When the editable option is disabled in the navigatable Grid and the user presses the 'Delete' button, the row is removed.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/xxZzRUbx
2. Click on a cell or navigate to a cell and press the 'Delete' button on the keyboard.

Current behavior

The row is removed, although the Grid is not editable.

Expected/desired behavior

The rows should not be removed in the non-editable Grid.

Environment

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

Bug report

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.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/HXzAIqWR/3.
2. Click in a cell and press Tab.

Current behavior

The cell is editable.

Expected/desired behavior

When the Grid is in readonly mode, it should not be editable when navigating using the tab key.

Environment

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

Bug report

Calling the Grid's addRow method throws an error.

Regression introduced with version 2025.3.812

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/bkGNMOMW/4
2. Click the Add a new row button

Current behavior

An error is thrown after adding the first row

Expected/desired behavior

No errors should be thrown

Environment

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

Bug report

Grid rows could not be properly selected on iPad

Reproduction of the problem

1. Open the dojo on iPad - https://dojo.telerik.com/gWsPhtrv
2. Try to select a row.

Current behavior

The rows could not be selected.

Expected/desired behavior

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

Environment

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

Bug report

When using the Grid's GetSelectedData method with a selectable column, the method throws an error.

Reproduction of the problem

1. Go to this Progress Kendo UI Dojo
2. Select a row
3. Click Get Select Data

Current behaviour:

The following error message occurs:

kendo.all.js:143633  Uncaught TypeError: Cannot read properties of undefined (reading 'selectedRanges')

Environment

Kendo UI version: 2025.3.812
Browser: [all ]