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):
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.
If a date column has a GridColumnMenuFilter, the filter drop down closes as soon as you attempt to open the date.
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.
When you scroll the linked above example there is a strange "jumping" of the rows.
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.
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.
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.
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.
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.
All Grid cells should be exported to PDF no matter if they have a template applied to their definition.
The "type" GridColumn prop is not available in the Typescript definitions available in the GridColumnProps.d.ts file.
The type prop should be available also in the Typescript context as it is available in this Knowledge base article
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.
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
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.
When the multicolumn header is locked it should not move along with the horizontal scrolling inside the Grid
We are currently upgrading the vue-gid-wrapper to the better native-vue-grid. Unfortunately some features, like the keyboard naviagation, don't seem to be included yet.
I assume the features from the wrapper will all be included in the new native grid, but to be sure I'm requesting the feature (naviagation).
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.
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.