Currently, the Native Grid Columns have the minResizableWidth property available in the API,

Can you provide a maxResizableWidth property that will do the same thing for the Grid's width but will limit its maximum width? 

Describe the bug
Locked and resized columns leave a small gap between the columns when scrolling is performed

To Reproduce
Steps to reproduce the behavior:
https://stackblitz.com/edit/mzxqs7-hy29kw?file=src%2Fmain.vue
lock both first and the second column from the column menu
resize the first column
scroll the columns

Curent -
A tiny gap is visible between the first and the second column

When using the chrome accessibility panel to inspect the filter operator button, there is no accessible name or title (hovering over the button does not give a tooltip with the name of the button).

The clear filter button does have an accessible name and title.

Please correct the filter operator button in order to meet WCAG Accessibility Standard 1.1.1 (Non-Text Content) and 4.1.2 (Name, Role, Value)

 

Hello there,

 

I am looking for a loading spinner solution to use with Vue Native Grid. I could not find something on the docs.

Is there any way I can show some kind of loading indicator while loading the data?

I am not using data source from Kendo, just basic method to populate `:data-items="items"`

 

Thank you!

Currently, the Native Grid implementation doesn't provide an option for the implementation of the scenario from the following screenshot. 

The thing that can be currently customized in the grouping toolbar of the Native Grid is only its text. 

Please provide an option by which we can define a custom template for the grouping toolbar.

 

Describe the bug
When having a scenario of Native Grid with a paging functionality, the pageChange event is being triggered when there is an interaction with the UI of the Pager.

When the user selects the number of rows per page, by choosing this value from a DropDownList, the object available in the event handler of the pageChange event has a value for its event property.

When the pageChange event is triggered by a change in the pages (1, 2, 3, etc.) the mentioned above event property has a value of undefined inside the event handler.

To Reproduce

1. Open this StackBlitz example
2. Change the number of items per page to 20.
3. Change the Grid page by using the page numbers
4. Check the browser's console

Expected behavior
The event prop should be defined no matter which element is triggering the pageChange event.

Describe the bug
When we use the Native Grid with a sortable configuration set to "{ mode: 'multiple' }" and we have a ColumnMenu, once the sorting functionality of the column menu is used, the sorting is reset.

To Reproduce

1. Open this StackBlitz example
2. Apply sort to the Name and Unit Price columns by clicking on each column header.
   
3. Select the column menu of the Discounted column and click the sort Ascending or Descending button.
   
4. Notice that the previous nested sort applied in the above steps is cleared and only the Discontinued column has an applied sorting.

Expected behavior

The sorting shouldn't be reset no matter which Grid sorting functionality is used. In the above example, the sorting of the Discontinued column should be added to the complex sorting.

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
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

Currently, the selectable property is available in the Wrapper Grid but not in the Native one. Please add the selectable functionality to the Native Grid.

Currently, the allowCopy property is available in the Wrapper Grid but not in the Native one. Please add the allowCopy functionality to the Native Grid.

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.

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.

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.

Scenario: Native Grid with Virtualization + Grouping.

The field for improvement: The expand/collapse is slow if we have a big number of items in the group which is expanded/collapsed

Example: https://codesandbox.io/s/smoosh-waterfall-7gebk1?file=/src/App.vue

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.

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?

 

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

 

 

 

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.