Describe the bug
The selectionChange & headerselectionchange events of the Native Grid component are unexpectedly triggered when filtering data in the component.

• The issue is not replicable on Chrome and Safari.

• A possible workaround for the bug is demonstrated in this StackBlitz example

To Reproduce

1. Open this StackBlitz project in Firefox
2. Enter random text in the filter input of some of the fields
3. See the following two errors in the console:

and

Expected behavior
No JS errors should appear when filtering the Grid component, no matter the browser that is used.

It would be beneficial if the Kendo UI for Vue ColumnMenu had an option to display the visible columns as it is in Kendo UI for Jquery, instead of creating a custom columnMenu:

https://demos.telerik.com/kendo-ui/grid/column-menu

The current implementation of the Native Grid doesn't support the row reordering functionality when the Grid is configured to work in virtualization mode.

Please provide the row reordering functionality in a scenario with virtual scrolling.

Describe the bug
The following warning appears in the browser's console when using the Native Grid in Nuxt context:

To Reproduce

1. Open this example
2. Check the browser's console

Expected behavior
No warnings or errors should appear in the console

In the current implementation of the GridColumnMenuCheckboxFilter component when its searchBox prop is set to true, the input that appears filters the component's values using the "startwith" filter operator. 

Providing a property that can define the filter operator of the searchBox inside the GridColumnMenuCheckboxFilter will be a very useful feature. 

Describe the bug
When we have a Grid that has a display: none CSS rule defined for it, switching to display: block makes the pager of the Native Grid be rendered in responsive mode as if the Grid is displayed on a small device.

Possible workaround:

• Set the pager's responsive property to false

To Reproduce

1. Open this project
2. Click on the button

Expected behavior
The Grid should appear on the screen and its pager should look like this:

while it is rendered like this:

The current implementation of the Native Grid doesn't provide the option to access its messages and use them in custom scenarios like Column Menu templates. 

Providing the option to take the components' messages would be a nice to have feature.

Describe the bug
The Native Grid looks differently when tested in development and production builds. Everything is OK in the development build and once the project is built for production, the Grid borders are missing.

To Reproduce

1. Download the Nuxt 3 Getting Started demo
2. Install the npm packages (npm i)
3. Run "npm run dev" and open the URL from the console. See the correct Grid look
4. Run "npm run build"
5. Run "npm run preview" and open the URL from the console. The Grid's borders are missing

Expected behavior
All styles should be available in the Native Grid, once it is built for production

Screenshots
Dev build:

Production build:

There are multiple smaller Kendo UI for Vue Native components used inside the Native Grid. In some scenarios, the fine-tuning of the smaller components is essential for the usage of the Grid. 

For example, the current implementation of the Grid doesn't provide an option to configure the formatting of the NumericTextBox displayed in the filter of its column menu. Now, to achieve the described functionality we have to use a custom column menu template.

Please add an option to control the configuration of the Native components used internally by the Grid.

Providing an Excel-like behavior inside the Native Grid will be a very nice feature for the component. The described behavior includes:

• Cells and rows selection like in Excel
• Editing like in Excel
• Keyboard navigation like in Excel

Currently, when we use a custom cell template, the rowIndex is not available inside the properties object when a specific row is in edit mode. 

If the visualized dataItem is not in edit mode the rowIndex is available in the dataIndex prop but this property disappears when the dataItem enters in edit mode.

Please make the dataIndex prop available no matter if a dataItem is in edit mode or not.

If the Grid is initialized with no items, the first call to resetTableWidth as part of the initialization sets the width style on the k-grid-table to 0px.

If any items are added afterwards this style remains, even though the autogenerated columns have a greater width. This leads to the grid not being visible until its size is set manually.

Sample (Grid demo with column definitions removed and changed load the data after mount instead of after creation): https://codesandbox.io/s/late-hill-rkdhc5?file=/src/Grid.vue

Add groupHeaderColumnTemplate, as in Kendo jQuery Grid and Kendo Vue Wrapper Grid, that can be applied as it is done in this demo https://demos.telerik.com/kendo-ui/grid/aggregates.

Describe the bug
The column virtualization functionality doesn't work when the Grid is configured to work in RTL direction.

To Reproduce

1. Open this StackBlitz example
2. No data is visualized inside the Grid
3. If we remove the :dir="'rtl'" configuration the Grid data is correctly displayed

Expected behavior
The Grid's column virtualization should work with both LTR and RTL configurations.

The current implementation of the Native Vue Grid doesn't provide an option to control the visibility of the column menu in each component column. 

Providing a property that can control the visibility of the different column menus will be very useful in scenarios when we want to create a customized column menu that contains a component with a popup. With the current implementation of the component, if we for example add a DatePicker to the column menu, the opening of the DatePicker's calendar triggers the closing of the column menu. Having a prop that controls the visibility of the column menu we can easily handle the described scenario. 

Describe the bug

When exporting the Kendo UI for Vue Native Grid data to a PDF file and the paper-size property is set to true, if there are locked columns inside the Grid, these columns are exported as empty columns.

• Workaround - a possible workaround is demonstrated in this StackBlitz example

To Reproduce

1. Open this StackBlitz example
2. Press the button above the Grid and save the exported file
3. Open the saved file and see how the locked columns have been exported

Expected behavior
All Grid columns should be correctly visualized in the exported PDF file, no matter if they are locked or unlocked.

Screenshots

Additional context
If we set the paper-size to a pre-defined value like 'A4', the issue is not replicable

Describe the bug
The value of the data-grid-row-index attribute of the different Native Grid rows is always -1, no matter the scenario in which the component is used.

To Reproduce

1. Open this StackBlitz example
2. Inspect a random Grid row and see its attributes

Expected behavior
The different rows inside the Grid should have different values for the data-grid-row-index attribute.

With the current implementation of the Native Grid, if one needs to set a minimum width to a column that needs to add the implementation suggested in this Setting a Minimum Column Width example.

While the approach in the above example works as expected, the logic that needs to be added can be internal for the Grid component. Thus the users will have to add a simple column property like the below and no other configuration should be set.

  {
    field: "ProductName",
    title: "Name",
    minWidth: 200
  }

Describe the bug
When the Grid's resizable property is set to true, the following test fails:

import { describe, it, expect } from "vitest";
import App from "../App.vue";
import { render } from "@testing-library/vue";

describe("App.vue", () => {
  it("renders apps", async () => {
    render(App);
  });
});

• The issue is not replicable if in Draggable.js file the:

import KendoDraggable from '@progress/kendo-draggable';

is changed with:

import { Draggable as KendoDraggable } from '@progress/kendo-draggable';

With this error:

To Reproduce

1. Open this project
2. Run 'npm install'
3. Run 'npm run test:unit'

Expected behavior
The test should pass as it used to pass in version 3.5.0, for example.