When user empty the filter field relative filter state must be spliced and not -> fieldfilter filtteraction emptystring and relative clear button disappear. If someone want to filter based emptystring there is specific action (isempty or notisempty) so no need to send to remote server a request with a value empty and make user confused about filters in action.

Hi , Can we have autocomplete feature in a Kendo GRID for angular so that when a user clicks on edit button to edit fields of a row ,the auto complete feature can be triggered on individual fields , also if this feature exists can some one please let me know about it . I couldn't find it in kendo grid documentation.

Given: a kendo grid with resize enabled.

And: the input locked on kendo-grid-colum  is undefined (by ex. due the component class property not initialized)

When: the user double click on the column resize handler 

Actual: the column width is set to 0

Expected: the colum  autofit behaviour remain consistent and set the column width as usual.

Previously igrid 5.0.0 introduced sortable column headers and their contents being wrapped in spans with inner cell and link classes

<span class="k-cell-inner">
       <span class="k-link>......

now after upgrading to 11.2.0 it looks like ALL column headers get this additional element nesting even if they aren't sortable which is greatly affecting how column headers display since .k-link has a display: flex value.  As well as many other styles.

Before

After

There are also "link" like styles applied to any and every column even if it doesn't sort giving the false impression that a column header is clickable.

This can be seen from kendo's own stackblitz for the grid https://stackblitz.com/edit/angular-lyxxa7?file=src%2Fapp%2Fapp.component.ts where if you inspect the header elements you'll see they've been wrapped in the sortable span elements. If this is intentional to wrap all column headers in we'll just have to work around it but we're curious if applying the sortable styling to ALL column headers was done on purpose or a bug.

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

The sort indicator (down arrow) remains after removing the sort (setting the [sort] input to undefined)

Thanks,

-Adam

I have being trying to implement the multiple row selection function but am unable to get multiple rows selected at once, even though I have multiple selected mode enabled,Is it possible to archieve this in Kendo ui grid in Angular?

Please see my function bellow. event=1 row always even though I select more one row.

There is a bug with the kendoGridGroupBinding directive when changing the input data and using virtual scrolling.  If you have many rows and scroll down to a lower virtual page and then change the input data to a small subset the grid will think there is no data.  And if you then change back to the full data set you have to start scrolling down before the grid repaints with data.  

Reproduction available here https://tyb2ys--run.stackblitz.io

Steps:

1. scroll down halfway in the grid

2. click the "Show subset" button.  Note the grid shows the no records message but should show three rows

3. click the "Show all" button.  Now the grid shows the scrollbar and the no records message is gone but it is not showing data.  You have to scroll down past where you previously were with all data before it repaints the rows

One workaround is to have an ngIf on the grid to destroy and recreate the grid when the input data changes, something like this:

Essentially the most basic GridComponent when ngIf'd in and out will not be collected -- apparently because of orientation change / resize change listeners not being appropriately removed.

Steps to Reproduce

Click the TOGGLE TABLE button to hide the table

Click the TOGGLE TABLE button to show the table

repeat several times

Take a memory snapshot

There will be HTMLTableRowElement items that grow each iteration of toggling the table.

The HTMLTableRowElements retention shows that they eventually lead to a resize listener, or an orientation change listener.

A built-in option for enabling a second scrollbar on the top of the Grid like the following screenshot would be nice feature to have:

Hi Team

It would be very helpful if Grid allow to prevent focus on cell out-of-box, at the moment, we have to handle focusin event then set focus to other cell, however when using navigation keys or shortcut key, we need to handle differently depend on which cell should be focus next.  

Reproduction

- Use a grid with data coming from a service (or another source)

- Click the delete button (built in with the grid

It removes the element from the grid as soon as I click the button but I want to remove it only after confirming the deletion.

Setting grid.columns[i].hidden may work to some extend, but isn't emitting columnVisibilityChange and further activities on a column set visible are not working but resulting in error, e.g. calling reorderColumn() results in:

TypeError: Cannot set property 'orderIndex' of undefined
    at GridComponent.push../node_modules/@progress/kendo-angular-grid/dist/fesm5/index.js.GridComponent.updateColumnIndices (https://localhost:4201/vendor.js:196833:43)

The grid internal method updateColumnIndices() throws an error, because it doesn't get the newly visible column from expandColumnsWithSpan() and expandedColumns.indexOf(source) is -1. 

Thus it's required to add methods like showColumn/hideColumn or setColumnVisibilty.

In Version 74.0.3729.108 (official Build) (64-Bit) of chrome, a defined grid with no predefined style property does not scroll properly. 

There is a live-demo on Stackblitz at https://stackblitz.com/edit/angular-b38r7s-jzsgty

This is a fork of the demo example from the kendo-angular-ui documentation available at

https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual/#

In the example, the scrollable grid was defined with a height property. This does not feet to our requirements, as we need a grid component that should flex according to the outside or parent container. 

This problem occured after the update of chrome browser from 73.0.XXX to the version 74.0.3729.108

The problem is fixed when we defined a grid with a height property like [style.height.%] = “100” but according to the documentation the grid should flex automatically without this property.