Please consider adding support for virtualization (e.g., virtual settings or similar) to the GridColumnMenuCheckboxFilter so that it can efficiently handle large datasets without performance hits.

Benefits:
 - Better performance with large datasets
 - Consistent UX with existing Kendo filtering components
 - Reduced need for custom workarounds

Hello,

there are numerous problems with navigating / scrolling on the DataGrid using keyboard keys.

Here is the test page:

https://stackblitz.com/edit/react-brdhufzd

1. Grid with navigatable=true:

- arrow keys - when you select a cell to be able to navigate and then  keep pressing down and then up, it's not posible to come back to the first record. You need to use the mouse.

- Page up/down keys work the other way round, also sometimes is not possible to come back to the first record, the scrollbar does not show the current position.

- It starts to work correctly after using the arrow keys and page up/down keys alternatively couple of times

2. Grid with navigatable=false:
- arrow,Page up/down keys and scrollbar work correctly

3. Grid with navigatable=true and nested inside Window:
- works the same way as not nested - the same problems occur

4. Grid with navigatable=false and nested inside Window:
- arrow keys move the window instead of navigating the grid
- Page up/down don't work at all

Add a Column Configurator that can be used to set the displayed columns and create multi-column headers

The new Built-in State Management does not work with remote data. 

For example:

PageSize = 40.
Remotely fetch 40 items.
Click on page 2.
Remotely fetch 40 items.
The grid shows no items, since items 41-80 does not exist in the data provided.

Verified with support who suggested adding a feature request.

As stated in the subject, the GridNoRecords component has an undocumented maximum width of 20em after which the GridNoRecords message is cut off. Please see the following StackBlitz for an example: https://stackblitz.com/edit/react-2z8hh63r?file=app%2Fapp.tsx

Kind regards,

David

To demonstrate:

1. Open your simplest interactivity/selection demo, which is not grouped, in StackBlitz. See: https://www.telerik.com/kendo-react-ui/components/grid/interactivity/selection/

2. Add the Grid's group prop. To demonstrate the bug nothing else needs changed

<Grid group={[]} ...

3. Run demo, scroll down and pick a row.

4. Observe the grid scrolls to the top and you cannot see your selected row unless you scroll back.

We use data grids with virtual scrolling for inline editing a large number of records. However, when we want to add a new row to the grid it automatically resets the scroll position and doesn't even fire onPageChange event so the records you see do not correspond to the scroll position.

Check the following example (scroll to bottom, click anywhere on the table - this will add a new row - and observe the described problem):

https://stackblitz.com/edit/react-52zzvz?file=app%2Fapp.tsx%3AL78

As a follow on to this bug:

Steps to reproduce:

• The "General Info" column has width setted to 500px

See Image 1.png

• resize it in the grid to make wider

See Image 2.png

• lock the "General Info" column
• scroll horizontaly

I am requesting a new feature so that "that the locked prop is passed by default to the child columns"

I think this would be a great feature to have out-of-the-box, and hopefully it's something easy to add from your end. UX-wise, it's really difficult to wrap your head around a non-alphabetized list, especially when the list is used for the special purpose of filtering -- you now have to filter down the list before you can filter the grid itself, which adds more overhead for the user.

I understand that Excel is not the end-all and be-all, but Excel also sorts it by default:

Full discussion can be found here - https://www.telerik.com/forums/how-to-make-gridcolumnmenucheckboxfilter-be-alphabetical-order

The GridHelper is defined in a separate file, and this is the way we can use it - https://www.telerik.com/kendo-react-ui/components/grid/getting-started/gridhelper/

However, I prefer if it is exported from the Grid package, and is maintained from there.

I have one column that contains mix of boolean and string values. When I attempt to apply a filter function to that column, it generates an error for the boolean value true because indexOf cannot be performed on a boolean. When I have other formats along with strings and I use filter="text", I would like the value to be converted to string in the filter function rather than modifying the data on my end before calling the filter function, because that would actually be incorrect data.

Example

https://www.telerik.com/kendo-react-ui/components/grid/filtering/

If I change

<Column field="Discontinued" width="190px" filter="boolean" /> 

to

<Column field="Discontinued" width="190px" />

and then search for anything in that filter it throws error.

Maybe if you make the `filter="text"` always convert the all the values to string values that would help resolve the error

Similar to how you can specify a column for the selection, it'd be nice if you could specify a column for the expand / collapse column so that you can provide a header value and handle a header value click change event.

The idea being that I could mass expand or collapse master detail rows similar to how I can mass select rows.