The user cannot select a filter operator if the filter input doesn't have entered data.
The user should be able to pre-select a filter operator no matter if there is data entered in the filter input or not.
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
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.
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
https://stackblitz.com/edit/tynxxg-vckenw?file=src/main.vue
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.
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.
Possibly provide more flexibility to the scenario
skip and cache are working correctly
Describe the bug
When using the GridPdfExport component for exporting Grid data to a PDF file the exporting operation fails with the following error:
To Reproduce
Expected behavior
A system dialog should appear asking where the generated file should be saved
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
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.
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
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
Expected behavior
The popup of the filter should be automatically closed when it is blurred.
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
Expected behavior
No JS errors should appear when filtering the Grid component, no matter the browser that is used.
When there is a custom cell template applied to a column in the Grid(Native), using the grouping functionality breaks Grid's layout
The Grid's layout shouldn't be affected if we apply a custom cell template
Package versions:
2019.2.621
Browser:
All
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.
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.
The styles of the Grid should not be changed when the scrollable property is defined.
Describe the bug
The @progress/kendo-vue-buttons is missing as peer to @progress/kendo-vue-grid package
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.
To Reproduce
Expected behavior
There should be a space between the different elements in the column menu -> filter popup
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
Expected behavior
The event prop should be defined no matter which element is triggering the pageChange event.
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.
Describe the bug
The following warning appears in the browser's console when using the Native Grid in Nuxt context:
To Reproduce
Expected behavior
No warnings or errors should appear in the console
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
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:
To Reproduce
Expected behavior
The Grid should appear on the screen and its pager should look like this: