Currently, if you double-click on the Grid resize handler the cell is not resized to auto-fit. It would be beneficial if auto-sizing was possible

There is an issue with white space that appears when you scroll a Grid with Groupable and Virtualization configurations switched on.
Reproduction:

1. Go to this article.
2. Scroll the Grid till the end of the scroller
3. See the white space.

Jumping issue:
When you scroll the linked above example there is a strange "jumping" of the rows.

• Bug report

Current behavior

https://stackblitz.com/edit/tynxxg-vckenw?file=src/main.vue

1. With the default code in the example, when first scrolling the skip is not accurate. If the grid is scrolled extremely slowly, you can see the skip is not incremented at first. If scrolling quickly, it is very jumpy.

2. The faster you attempt to scroll, the stranger the skip behavior becomes unlike with simply removing the grouping grid prop in the same example. I've been able to get into situations it in the provided StackBlitz by scrolling down and scrolling back up quickly where it hangs on row counts and where it will scroll past the 0 indexed row causing an empty grid, then scrolling down again with either jump with a large skip number or sometimes throw an error.

3. Possibly provide more flexibility to the scenario

Expected behavior

skip and cache are working correctly

Hello Team.

I appreciate grid's reorderable function work at Nuxt3(@kendo-vue-grid: 3.14.2).

But For some reason, this function doesn't work properly. so I report a bug.

I reproduce a stackblitz code.
https://stackblitz.com/edit/nuxt-starter-gmag5m

I implemented it like this,

After fetching(=GET) column data from the server, reorder the columns using kendo grid's reorderable function and save(=POST) it on the server.

I call columnExecute function, so server refetch(=GET) column data.

at /pages/index.vue, colums ref change rightly.

at /components/grid.vue, columnList ref change rightly.

But rendered kendo grid's column doesn't change.


please check this issue. 

 

Sincerely,
Eunbyul.

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
Resizable and reorderable true does not work in nuxt
https://stackblitz.com/edit/hy923e-fmrqsf?file=package.json
Try to resize or reorder

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

Describe the bug
The @progress/kendo-vue-buttons is missing as peer to @progress/kendo-vue-grid package

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.

Describe the bug
When using the GridPdfExport component for exporting Grid data to a PDF file the exporting operation fails with the following error:

• The issue is replicable only when working in Vue 2 context

To Reproduce

1. Open this CodeSandbox example
2. Click the button above the grid

Expected behavior
A system dialog should appear asking where the generated file should be saved

Describe the bug
When using a slot template inside the Grid, the content of the template should always have only one DOM element on the root level. If there are multiple elements on the root level, only the first element will be rendered.

In scenarios when we add a comment inside the slot template as a first element, the Grid recognizes it as the first element in the template and nothing will be rendered.

To Reproduce

1. Open this StackBlitz example
2. See the Unit Price column

Expected behavior
The rendering of the slot template shouldn't depend on the number of root elements inside it. The template should be rendered in scenarios with both single and multiple elements in the root.

Screenshots

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
A clear and concise description of what the bug is.

To Reproduce
https://codesandbox.io/p/sandbox/beautiful-tristan-5nvvfy?file=%2Fpackage.json
open the console and click the export button.

Expected behavior
No error in console