Please provide a feature allowing to set the "role" attribute to cells (TD elements) in a given Grid column.

Hello,

The list view component provides a loader template. This is easier to work with than the mechanisms provided for the grid component. For the sake of consistency of approach, I would like to request that a grid loader template directive be provided for the grid component, similar to the one available for the list view that is seen here: https://www.telerik.com/kendo-angular-ui/components/listview/api/LoaderTemplateDirective/

Please provide a built - in rows reordering functionality that isn't based on the public HTML drag and drop api. Also please allow to customize the content of the drag hint. Something similar to the drag and drop feature of the TreeView.

thank you

Hello team,

Could you please assist me with gaining understanding of implementation of the drag and drop Angular feature together with your grid?

I need to implement the following scenarios:

1. D'n'd between 2 Kendo grids in different components
2. D'n'd between Kendo grid and custom list in separate component
3. D'n'd in scope of the same Grid.

Lets say I have Angular of the 8th version and the latest version of Kendo Angular Grid.

It would be very cool if you can update your documentation with the corresponding page.
If that doesn't make sense from your perspective I would appreciate if you could provide me detailed instruction for all the above scenarios implementations.


Thank you in advance.

Can you please consider adding a built-in option for freezing Grid rows that will always stay below the headers area during scrolling?

Hello,

 

As I explained in this post, I would like to set max-width on certain columns of a grid to force them to not becoming bigger than a certain size if there is a remaining width in the parent container. However, I do need to distribute the remaining width across other columns if they don't have max-width.

 

For example in this project https://stackblitz.com/edit/max-width-request?embed=1&file=app/app.component.ts, I want the first column which shows the ID of products would never be bigger than 15. I'm advised to leave one of the columns without setting width, so that column will occupy the remaining width and as a result the width of columns with width will be respected as max-width. However, that is not good because in big screens you will end up with a very big column while other columns are still suffering from lack of space.

 

Thanks,

 

Mojtaba

When using KendoUI for Angular 2+, the filter value is still enabled and accepts input when "Is null" or "Is empty" is selected.

Since those selections do not require a parameter, I'd prefer the filter value to be default disabled.

 

I'm seeking support here to lock kendo angular grid column separately. As I can see that, all locked columns are in a div and unlocked are in another div. Is there any possibility to lock some columns are in left and some are in right? Attaching my design requirement here for more info.

Would like the ability to programmatically expand or collapse all groups for all rows in the grid.  Without having the need to iterate across all rows.

I need to expand/collapse grid rows programmatically. I know about grid.expandRow/collapseRow, but there is no public methods which can get me know  is row expanded at this moment and collapse it. I need to manage in component array of expanded rowIndexes and every time to check is row expanded,then call method collapseRow, which again, under hood, using your private method this.detailsService.isExpanded(index), is doing this check. It's very inconvenient.  So, can you expose this methods or toggleRow() to allow us get rid of additional logic around? Or, possibly, you know other way to get this info directly from grid?

It would be nice to have support for horizontal virtual scrolling for the Grid in cases of large number of columns. Just like the current feature for vertical scrolling, in which you can update the visible rows through a pageChange() event handler.

Currently in the Grid, the GroupHeaderTemplate can create just one cell. I'd prefer to have option to have columns in the group header like it is implemented in the jQuery Grid. Check it here https://demos.telerik.com/kendo-ui/grid/aggregates
This option will be handy for displaying aggregates in a group header.

when expanding a group, inside the expand event (function) we do have access to the groupIndex.

but groupIndex is not available inside the groupHeader(Footer)Template itself.

we need that groupIndex, so we can get the parent items (groups) to the group that is expanded.

Currently the pager is always at the bottom of the grid. I would love to see an option to place the pager at the top and/or bottom. Without adding custom code every time I need this.

When using virtual scrolling and grouping features (currently achieved with kendoGridGroupBinding directive), the ability to control the expanded state of the groups is disabled due to limitation.
The available methods are helpfull when you want to control the state of the groups at runtime, but are not compatible with virtual scrolling since the records are loaded on demand. 
It would be nice if we had the ability to collapse and expand all groups of the Grid programatically when using virtual scrolling.

We need to store column's show and hide state when apply from ColumnMenuChooser component.

I opened this question

https://stackoverflow.com/questions/51331725/kendo-grid-for-angular-2-reactive-formarray

Would be nice to make grid reactive more transparent, or make a complete example to use it.

Introduce support for Loading / Error templates for components. eg.:

<kendo-grid [success]="boolean" [loading]="boolean>
  <div kendo-error-template>
   We Cannot load your data
  </div>

 <div kendo-loading-template>
    <!== some kind of spinner, or just text>
  </div>
</kendo-grid>

I find myself reusing similar/identical code in order to implement filtering, sorting and virtual paging. In almost all cases, I am simply applying the filters, sort and determining the records to select based on the page as shown in the API.

This code should be inbuilt into the kendo grid. If filterable is true, kendo should implement the filter change event and apply filters automatically; the users should not be forced to define what happens on filter change for every grid instance. Similarly, if sortable is true, the kendo grid should automatically implement default sort functionality.

The same would also be useful for virutal scrolling. If scrollable is set to 'virtual', then the view to be shown in the grid should be automatically calculated on page change.

If the value "-1" is passed in as one of the values in pageSizes input for the PagerPageSizesComponent, that option should be shown as "All" and should show all rows available for the grid.