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
In a scenario of Native Grid with Filter row once the filter popup is opened, the only way we can close it to select a value from the dropdown.

To Reproduce

1. Open this StackBlitz example
2. Click on the icon next to a random input in the filter row
3. Click outside the popup that appears in step 2.

Expected behavior
The popup of the filter should be automatically closed when it is blurred.

Screenshots

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

Describe the bug
In scenarios when we dynamically add data to the beginning of the Grid, the component re-renders elements whose re-rendering can be skipped.

To Reproduce

1. Open this StackBlitz example
2. Click on the "add row to beginning" button

Expected behavior
The onUpdated method should not be called when adding a new row to the beginning of the Grid. Instead, if you open the browser's console, the result is that "updating..." is logged three times.

In my project, I always use remote data because the data comes from a backend that aggregates data from several sources in the company and because I want to sort, filter, etc on the server to be able to do it on the entire dataset (and I cannot do it in the frontend because it's a lot of data).

In the Wrapper Grid, we can add a "Refresh" button to the pager of the component using the pageable-refresh property. 

Such property is not available in the Native Grid. As the Native Grid doesn't use the DataSource component, I can assume that the Refresh button cannot be fully functional out of the box but still we could be able to pass a method that will be triggered once the button is clicked. Then through this method, we can make an API call and update the data.

Scenario: Native Grid with Virtualization + Grouping.

Describe the bug
The layout of the column menu popup window, inside the Native Grid, is different when using version 4.x.x and version 5.x.x. of the Kendo Themes.

• The issue is replicable with all Kendo Themes

To Reproduce

1. Open this example
2. Click on the column menu of the Name column
3. Inside the column menu, click on "filter"

Expected behavior
There should be a space between the different elements in the column menu -> filter popup

Screenshots

Describe the bug
With version 3.0.4 of the Grid component, there is a regression in the way the component displays date fields.
Till version 3.0.3, date fields defined like '2021-05-13T00:00:00' were correctly displayed. From version 3.0.4 fields defined as '2021-05-13T00:00:00' are not displayed in the Grid.

To Reproduce
Steps to reproduce the behavior:

1. Open this StackBlitz example
2. See the 1st and 3rd row in the Date column

Expected behavior
All dates in the Date column should be visible as in this StackBlitz example.

Describe the bug
If you try to group the data in a Grid by a column that has a value of "null", the browser hangs, and an error appears in the console.

To Reproduce

1. Open this StackBlitz example
2. Group the Grid by "Unit Price" field

Expected behavior
The data should be grouped according to the values inside the UnitPrice column. A column with an empty header should appear for the group with a "null" value.

Screenshots

Workaround

Convert the "null" values to empty string with a code like this:
this.products.forEach((o) => { o.UnitPrice = o.UnitPrice === null ? '' : o.UnitPrice; });
Here is a modified example in which the above code is added to the getData method.

Describe the bug
When you use the filterGroupByField method, if there are more than 2 filtered items, the method returns null. If the filtered items are one or two, the method works correctly.

To Reproduce

1. Open this StackBlitz example
2. Open Browser's console(F12)
3. Click on the "ProductName" column menu and select 3 or more checkboxes
4. See the output in the console which is "null"

Expected behavior
The result returned from the filterGroupByField method should be with a structure similar to the below one, no matter how many checkboxes have been selected in the column menu.

I want to use filterGroupByField to indicate that a column that has a GridColumnMenuCheckboxFilter.  Naturally, there can be more than 2 items selected.  If more than 2 items are selected, the filterGroupByField returns null.

See this example (select more than 2 product id's):

https://stackblitz.com/edit/i58xwv?file=src/main.vue

If a date column has a GridColumnMenuFilter, the filter drop down closes as soon as you attempt to open the date. 

Reproduction steps:

Add a GridColumnMenuFilter to a column that is defined as a date.  Upon opening the filter and attempting to select a date, the filter immediately closes.  

This example has the problem reproduced. https://stackblitz.com/edit/zdmtjk?

In this example the 'expanded' prop is set to true by the filter is not expanded - https://stackblitz.com/edit/uquwh8-1e5npd?file=src/ColumnMenu.vue

a possible workaround - uncomment the line in the mounted function.

Add functionality that allows the users to configure the Native Grid's Pager in a way it has the "All" option in its page sizes DropDownList.

The "All" option is available in the Kendo UI for jQuery suite(check the second example on the page). When the "all" option is selected, all Grid records are loaded on one page.

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.

I'm submitting a...

• Bug report

Current behavior

If a column has a value of 0 and there is no editor defined for this column, when editing Grids' data, the input in which 0 should be displayed is actually empty.

Expected behavior

When editing the Native Grid, the data displayed when a row is not in edit mode should be the same as when the same row is in edit mode.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. Edit a row whose UnitPrice value is 0
3. See the empty input for the UnitPrice field, when the selected row is in the "edit" mode

I'm submitting a...

• Bug report

Current behavior

When a named slot template is used in the Grid, the PDF export functionality will not export the cells that have an applied template.

In the linked below example, after exporting the Grid to PDF, the header cell of the "UnitPrice" column is empty.
If you remove the headerCell: 'headerTemplate' configuration and export the Grid to PDF, everything is exported correctly.

Expected behavior

All Grid cells should be exported to PDF no matter if they have a template applied to their definition.

Minimal reproduction of the problem with instructions

1. Open this project.
2. Click on the "Export vie PDF component" button
3. Check the exported file