Providing an Excel-like behavior inside the Native Grid will be a very nice feature for the component. The described behavior includes:
Describe the bug
The @progress/kendo-vue-buttons is missing as peer to @progress/kendo-vue-grid package
It would be beneficial if the Kendo UI for Vue ColumnMenu had an option to display the visible columns as it is in Kendo UI for Jquery, instead of creating a custom columnMenu:
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.
The pagination on the jquery grid is responsive by default with the ability to turn off responsiveness if desired. https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/pageable.responsive
It would be useful to add responsiveness to the pagination on the Vue Native Grid with the same ability to turn it off if desired.
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.
Currently in the Vue Native grid, you can only specify column widths in pixels.
This becomes problematic if the user has their browser font size set to a larger size. Since our font size, padding, etc. are using responsive rem units for sizing, they properly resize to a larger size, but since the column widths are set in pixels, the now larger filter fields and buttons don't fit appropriately in the alloted space (see below screenshot). For smaller columns, you can't even see what you've typed into the filter field.
In the screenshot, the larger font size was set in Google Chrome by going to Settings > Appearance > Font size > Very Large.
This enhancement would be helpful to ensure improved accessibility for those who need a larger font size in order to read the text.
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
onRowClick not there in Vue Grid
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.
It will be very helpful if there is an example that demonstrates how we can copy and paste data from Excel to Kendo UI for Vue Native Grid.
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?
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
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.
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
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.