In OData 4.01 the 'in' operator was introduced (https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_In). Can this also be implemented in the toODataString function?

Currently, the auto resize of the the columns does not take the width of the grid into account.  I don't think this is how most users would expect this to work.  The autofit of the columns should be able to resize the columns so that they work as best they can within the grid's bounds.

Now, when I autofit my columns, the first thing I have to do is resize the columns manually so I can see the whole row on the screen.  Since I end up resizing the columns manually anyway, autofit ends up not really helping me much.

Some toolkits I have used have a resize mode for a table which determines whether or not all columns are to always be visible or not.  If all the columns are to always be visible, resizing one column needs to resize the others so that everything still fits.  This "mode" could determine which algorithm autofit should use

Hi Telerik,

It would be great if we can add Select All functionality as a built-in feature of the MultiSelect component. It is especially useful when working with checkboxes, e.g., https://www.telerik.com/kendo-angular-ui/components/dropdowns/multiselect/templates/#toc-rendering-item-checkboxes.

The cols and rows property in the GridLayout can only be an array of strings and/or numbers. Please add the ability to use a min function something like: [cols]="[145, min(145, auto)]" or [cols]="[145, min(145, 12%)]"

Hi,

It will be very useful if an Azure layer is provided to the Map component, similar to the Kendo UI for the jQuery map widget:

https://demos.telerik.com/kendo-ui/map/azure 

 

Currently, if you use Shift to select rows 3 through 6, then clear the selectedKeys array, and later perform a new Shift-click selection on row 9, the selection includes rows 6 through 9.

Add a method to reset the selection state so the next Shift-click starts from the default rangeSelectionStartRow instead of the previous selection.

Introducing a compact mode in the component would help prevent unused empty space. There is an existing Kendo jQuery feature request with a significant number of votes.

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. 

The default item approach is not suitable for some of our UX use cases.

In firefox, open the Kendo Radio Button documentation and slowly resize the window (https://www.telerik.com/kendo-angular-ui/components/inputs/radiobutton)

The radio button will kind of jiggle around and occasionally the white dot in the radio button will become off-center.

This also seems to happen in response to some material bouncy (cubic-bezier) animation transitions.

Currently the Grid doesn’t offer a way to disable the pager adaptive mode.  This would be a useful feature for applications and use-cases where the pager’s adaptive mode isn’t desired.

The Angular Grid export only includes PDF and Excel formats. Requesting an enhancement to be able to export to CSV for purposes of opening the data in a text editor other than Excel or to allow for easier upload into other applications.

There are articles that show how to do this but it would be better out of the box from Telerik.

https://stackblitz.com/edit/kendo-angular-grid-csv-export?file=app/app.component.ts

https://www.codeproject.com/Articles/5162666/CSV-Export-In-Angular-with-Kendo-Control 

 

 

Please provide an option to expand row axes by default. The functionality should allow rendering the row axes expanded just as if they were expanded by clicking on their expand arrow.

Thank you.

The current FilterService does not handle nested composite filter descriptors, ignoring them and only processing individual filter descriptors. This limits functionality, especially for complex filtering scenarios. The request is to enhance FilterService to fully support and process nested composite filter descriptors.

Look at the notes for use cases.

It might be a formatting issue on my end

 

Hi ,

I want the kendoGridFocussable to apply the FocusableDirective on an anchor tag. This should allow the user to reach the anchor element using only the arrow keys without pressing Enter. (Example : Please, check out the following StackBlitz demo: https://stackblitz.com/edit/angular-rqqzam)

Regards,
Uzma

Hello,

When I try to delete all grouping manually by setting an empty group array, datas are disappearing. The grid datas are empty but reappears if I set grouping again. Also I could see data if I scroll down but I can't see any if I haven't enough lines to do so.

In attachment you could find a demo based on the "Collapse All with Grouping" tutorial.

Hi,

It will be a good addition to the CheckboxColumnComponent if you allow developers to disable the checkboxes conditionally.

Workaround adding `k-disabled` class using class and headerClass properties:

https://stackblitz.com/edit/angular-n4gpjp-xqkpjz?file=src%2Fapp%2Fapp.component.ts

 

Feature to add "Select All" option in the Column Chooser of the Grid.

Similar to the feature in jQuery Grid: Display SelectAll in the ColumnMenu for Showing and Hiding Columns | Kendo UI Grid for jQuery | Kendo UI for jQuery (telerik.com)

First of all, thank you for providing the state management feature. For me it's one of the most important features of a grid component.

But unfortunately it fails to restore the columns state. This is because each time a grid component and it's columns are instantiated, new IDs are created for the columns. When loading state the columns are identified by their IDs.

When a column is persisted with e.g. id 'k-grid-column-1' and the grid will be destroyed and re-created, then the new column ID is not identical with the old one. Thus restoring the column's state will fail.

Please have a look to this StackBlitz example: https://stackblitz.com/edit/angular-vauqyshn?file=src%2Fapp%2Fapp.component.ts

A possible workaround is to save also the column's field property and later use it to re-map the saved id to the new id.

A better solution may be to extend the GridColumnComponent with something like a "PersistenceKey" property, which will be used for identifying a column. A directive may also work. Otherwise generating non transient unique ids for the grid columns will also work.

Best regards,
Holger