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.
The last saved item is moved to the end of the Grid
1716706
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!
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).
Thanks & Regards
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!
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.
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.
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.
Hi Team,
I would like to request a way to hide all columns with the columnMenu instead of requiring one to remain.
Thank you!
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 Grid has scrollable.virtual enabled and pdfExport.allPages set to true, the loader is actually displayed, but it gets hidden immediately when the next page is loaded for exporting. This leads to the loader appearing as not visible. https://dojo.telerik.com/QlIlIbTZ
I would like the progress bar functionality to be improved and to have built-in support for displaying a progress bar in the virtual Grid when exporting all pages
Hi Team,
I would like to request more live demos/samples which use Kendo UI for jQuery in ASP.NET Core web applications.
Thank you!
Hi Team,
I would like to request a way to be able to pass a string value to a numeric column without schema.parse or changing the model to object. This would allow us to use all sorts of functions/behaviors related to the number type (filtering, editing, etc.).
Thank you!
Hi Team,
I would like to request for the Grid the functionality to allow copying but to be able to configure row or cell copying without being dependent on selection mode. For example, a grid with multiple/row selection, but configured to select a cell.
Thank you!
Hi Team,
I would like to request the Kendo UI Grid's navigation should focus on the <tr> element instead of the cell for a true row-level keyboard interaction.
Thank you!
Hi Team,
I would like to request a way/demo to have AutoSync for the dataSource and be able to stay in edit mode in the Kendo UI Grid.
Thank you!
When the Grid is in RTL mode and has horizontal scroll it does not autoscroll when the user try to reorder columns.
The horizotnal scroll does not move when dragging. In non-rtl mode the horizontal scroll autoscrolls while dragging a column.
The behavior in RTL mdoe should be consistent with non-rtl. The horizontal scroll should move when dragging a column.