The multiCheckbox filter popup in the Grid sorts its distinct-value list using JavaScript's native string comparison, which orders characters by Unicode code point. This produces correct results for ASCII-only data but breaks for any locale whose alphabet includes characters outside the ASCII range (Turkish İ/Ğ/Ş/Ö/Ü/Ç, German ä/ö/ü, Czech/Polish diacritics, etc.).
The request is to sort the filter item list using locale-aware comparison (`String.prototype.localeCompare`) so that values appear in the correct alphabetical order for the active language, or provide a custom way to order the filter options.
Dynamic grid status content does not announce updates to screen readers during filtering or pagination.
For example, the status message “1 – 4 of 4 items” updates visually but is not announced to assistive technology users.
As a result, screen reader users do not know when filtered or paged results change.
This can be improved to read out how many items are left on the page for the user to navigate them, as in some cases, there might be none.
Similar to Kendo jQuery:
https://www.telerik.com/kendo-jquery-ui/documentation/controls/grid/grouping/group-paging
https://demos.telerik.com/kendo-ui/grid/server-grouppaging-virtualization
The implementation should also be compatible with the MVC helpers like: https://www.telerik.com/aspnet-mvc/documentation/api/kendo.mvc.ui/datasourcerequest
Highlight the Filter option in the Column Menu when a filter is applied to the column, similar to how the Sorting option is highlighted. This helps users recognize when a filter is active and keeps the design consistent with the sorting highlight.
Workaround - https://stackblitz.com/edit/angular-2ugqhdk3
Current rendering:
Desired rendering:
Our use case is a "search filter" grid:
This "search filter" has the following characteristics:
1) It can potentially result in 1000's of rows being "found" by the search criteria, the actual search is done by the server using various HTTP(S) REST API's.
2) Obviously we only load a small initial number of rows from the server and then as the user scrolls down we load additional rows from the server as required.
3) The initial load of rows and the incremental subsequent load of rows are all done asynchronous using various HTTP(S) REST API's, so the new rows arrive asynchronous. While loading rows, the user is allowed to scroll freely in the already loaded rows. For the rows being loaded we show skeleton rows if the user scrolls into the area of the "search filter" currently being loaded.
We would request a update to the Kendo Grid libs. to support concurrent scrolling, loading of data (trough the pageChangeEven) and virtual rows & columns, all at the same time.
Hi,
we would like to submit a feature request for the grid component:
We would like the tds (generated when the kendoGridGroupHeaderColumnTemplate is specified) to be sticky if the related column is sticky (since right now, if i stick a grouped column, the group row td corresponding to the sticky /locked column scrolls with the rest of the row instead of being sticky as we would expect)
here's an exaple of the behavior we are encountering:
https://stackblitz.com/edit/angular-lgbef6c1?file=src%2Fapp%2Fapp.component.ts
Best regards,
Claudio Salvatore Conte
Provide a built-in column menu component (like in the Grid and TreeList) for the base column menu functionalities - filter, sort, sticky. This way, custom column menus can be easily created when you want to keep some of the default options.
Right now, I need to create all components, even those for filter and sort, from the ground up, but available as:
kendo-grid-columnmenu-filter
kendo-grid-columnmenu-sort
is the Grid.
It would be a useful improvement to the date filtering if developers had the option to exclude the time portion when filtering dates in the Grid.
This can be a property like includeTime with a default value, and the developers can choose to include or exclude it.
It would be great to have column highlighting in the Grid, so when a user hovers over a cell, the entire column, including the header, is highlighted. Something similar to the example below, but built-in, would provide a better experience for both users and developers.
https://stackblitz.com/edit/angular-ink98nn6?file=src%2Fapp%2Fapp.component.ts
Currently, the pageSizes option of the available Grid's PagerSettings only allows passing a boolean or a number array as possible values. Thus, at the moment, the Grid component allows displaying an "All" option in the pager by implementing a kendoPagerTemplate:
It would be great if an "All" page size option could be set directly through the settings of the pageable property by having the ability to pass a PageSizeItem array to the pageSizes option, similarly to how its done in the standalone Pager component:
The Grid provides column spanning by default, but the change is applied to all rows:
https://www.telerik.com/kendo-angular-ui/components/grid/columns/spanned
A good addition to the Grid would be to provide conditional columns spanning where some rows are normal while others - have spanned columns such as:
Provide a built-in feature to collapse or expand child columns of the group column similar to ag-grid.
Workaround using the header template: https://stackblitz.com/edit/angular-orwl7wza
Currently, the NumericFilterMenuComponent has a default filterDelay of 500ms. So, in some scenarios where a value is entered and the Enter key is pressed very quickly, the component may not be able to catch the new filtering condition and create a new filter descriptor with the entered value.
It would be great if the component is enhanced to take into account the last entered value in such scenarios despite the defined delay.
When grouped data contains a large number of columns, processing the aggregates takes significant time resulting in freezing for a couple of seconds when grouping virtualized Grid by certain column fields, e.g.:
https://stackblitz.com/edit/angular-7zdydotc-h3caizxo?file=src%2Fapp%2Fapp.component.ts
It would be nice to have a feature to remove some operator from the grid filter built-in functionality as a global setting so that they apply across all grid columns without needing to repeat this customization for each column.
I understand that Kendo supports this functionality as described, but my expectation is to configure it as a global setting rather than on an individual basis. This would significantly simplify configuration in cases where multiple grids or columns are involved.