I'm submitting a...

• Bug report

Current behavior

The user cannot select a filter operator if the filter input doesn't have entered data.

Expected behavior

The user should be able to pre-select a filter operator no matter if there is data entered in the filter input or not.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. In the Product Name column, I click the filter operator button
3. Select "Ends with"
4. Click the filter operator button again and see that "Ends with" is not selected.
5. Type "g" in the filter text field. Grid updates but doesn't filter the data by "Ends with" filter.
6. Click the filter operator button and see that "Contains" is selected instead of "Ends with"
7. Select "Ends with" once more and Grid filters correctly

• 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

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

Goodmorning Progress,

We're working quite some time with Kendo for Vue and we are slowly migrating some old 'wrapper' grids to the new native grids. We know there are some limitations in it, because not everything is developed yet, but that wasn't a show stopper for us.

Or project uses quite a lot of data (like a google sheet) and we need it to be editable. So we implemented a native grid and a custom cell render with a VueComponent. This works perfect in case of a little amount of cells, but when there are more rows and columns it's giving us some performance issues.

First we tried virtual scrolling, but this feel 'honky-bonky' and is not even workable on a mac. Then we tried column-virtualization to minimize the rendered data, but also that didn't work. Columns aren't re-rendered when visible and its conflicting with our three locked start columns (visually data overlapping, numbers go through each other, etc).

Then our options are down to zero, so i started to investigate with some performance profiling what's happening. In our case we have 70 columns and 500 rows, this results in like 35k cells. Rendering isn't the big issue, until u start interact with the grid. Our RowClick-function sets one item in the data-items to 'inEdit' like the docs also showing. When this is happening the page freezes and i start wondering why. I found out that ALL the GridCell's (with a custom CellRender) are calling the updateRender-function. So 35k functions are called in some milliseconds and causes it to freeze. It takes around 30 sec's to get it a bit reactive, but you can understand its not workable anymore.

Our wrapper grids hadn't a single problem with handling these kids of data (no paging, no weird stuff, also custom renders for every cell)

Can you please provide me an answer why this is happening? It's possible to get access to our test-environment with the grids in action to visualize my problem a bit better. 

We have a payed license on a co-worker account (berend.haan@..).

Kind regards, 
Sander

The Accessibility Support page for Kendo UI for Vue Native Components (https://www.telerik.com/kendo-vue-ui/components/accessibility/accessibility-compliance/) incorrectly implies that the Vue Native grid has keyboard navigation support. The page seems to be referring to native components as seen by the breadcrumb and the introduction text.

All of the items in the list except for the grid are linked to the Vue Native component. The "grid" item is linked to the Vue Grid Wrapper (https://www.telerik.com/kendo-vue-ui/components/grid-wrapper/keyboard-navigation/).

I believe there's already a (unplanned) feature request out there to add keyboard navigation features to the native grid, but in the meantime, please remove the grid from this page as it does not currently support full keyboard navigation.

I'm submitting a...

• Bug report

Current behavior

If the scrollable property of the Grid is set to 'null' the header of the Grid changes its background styles a column width, compared to when the property is not set.

Expected behavior

The styles of the Grid should not be changed when the scrollable property is defined.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example.
2. Remove the :scrollable="'none'" property definition from the Grid and see how it changes

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?

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
The @progress/kendo-vue-buttons is missing as peer to @progress/kendo-vue-grid package

When using a grid with a selectable column and keyboard navigation enabled, it's not possible to select the last visible row. Instead of selecting the row, the grid just scrolls the item to the center of the grid.

I've attached a gif of the behavior and a sample project based on the grid demos.

I'm submitting a bug report

Current behavior

In a Native Grid that has a multicolumn header which is locked, when the Grid is scrolled horizontally, the upper(shared) part of the multicolumn header is moving based on the scrolling direction.

Expected behavior

When the multicolumn header is locked it should not move along with the horizontal scrolling inside the Grid

Minimal reproduction of the problem with instructions

1. Open this example
2. Scroll the Grid horizontally

I'm submitting a...

• Bug report

Current behavior

The "type" GridColumn prop is not available in the Typescript definitions available in the GridColumnProps.d.ts file.

Expected behavior

The type prop should be available also in the Typescript context as it is available in this Knowledge base article

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

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.

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.

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
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
Grid rowRender is triggered for every more than once in in-cell editing scenario vue 2

To Reproduce
https://codesandbox.io/s/confident-wind-50llik
1 Click on some cell
Current: RowRender is triggered for every row
Expected: RowRender is triggered only for the clicked row

Describe the bug
There is a blank space at the bottom of the Grid when the user scrolls the data. This blank space appears on a specific configuration where the Native Grid is configured with virtual scrolling and the groupable property is set as follows:

:groupable="{ footer: 'visible' }"

• The issue is replicable in both Vue 2 and Vue 3
• The issue is not replicable if the groupable prop is defined like this:

:groupable="true"

To Reproduce

1. Open this StackBlitz example
2. Scroll the data items to the bottom of the Grid

Expected behavior
There shouldn't be any white/blank spaces at the bottom of the Grid

Screenshots