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 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.
Describe the bug
When the Grid's resizable property is set to true, the following test fails:
import { describe, it, expect } from "vitest";
import App from "../App.vue";
import { render } from "@testing-library/vue";
describe("App.vue", () => {
it("renders apps", async () => {
render(App);
});
});
import KendoDraggable from '@progress/kendo-draggable';
is changed with:
import { Draggable as KendoDraggable } from '@progress/kendo-draggable';
To Reproduce
Expected behavior
The test should pass as it used to pass in version 3.5.0, for example.
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' }"
:groupable="true"
To Reproduce
Expected behavior
There shouldn't be any white/blank spaces at the bottom of the Grid
Currently, when we use a custom cell template, the rowIndex is not available inside the properties object when a specific row is in edit mode.
If the visualized dataItem is not in edit mode the rowIndex is available in the dataIndex prop but this property disappears when the dataItem enters in edit mode.
Please make the dataIndex prop available no matter if a dataItem is in edit mode or not.
We are currently upgrading the vue-gid-wrapper to the better native-vue-grid. Unfortunately some features, like the minScreenWidth, 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 (minScreenWidth).
columns: [
{
field: 'variableName',
title: 'fieldTitle',
width: '125px',
minScreenWidth: 1000
},
...
]
The current implementation of the Native Grid doesn't support the row reordering functionality when the Grid is configured to work in virtualization mode.
Please provide the row reordering functionality in a scenario with virtual scrolling.
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:
The current implementation of the Native Grid doesn't provide the option to access its messages and use them in custom scenarios like Column Menu templates.
Providing the option to take the components' messages would be a nice to have feature.
Describe the bug
The Native Grid looks differently when tested in development and production builds. Everything is OK in the development build and once the project is built for production, the Grid borders are missing.
To Reproduce
Expected behavior
All styles should be available in the Native Grid, once it is built for production
If the Grid is initialized with no items, the first call to resetTableWidth as part of the initialization sets the width style on the k-grid-table to 0px.
If any items are added afterwards this style remains, even though the autogenerated columns have a greater width. This leads to the grid not being visible until its size is set manually.
Sample (Grid demo with column definitions removed and changed load the data after mount instead of after creation): https://codesandbox.io/s/late-hill-rkdhc5?file=/src/Grid.vue
Describe the bug
The column virtualization functionality doesn't work when the Grid is configured to work in RTL direction.
To Reproduce
:dir="'rtl'"
configuration the Grid data is correctly displayedExpected behavior
The Grid's column virtualization should work with both LTR and RTL configurations.
The current implementation of the Native Vue Grid doesn't provide an option to control the visibility of the column menu in each component column.
Providing a property that can control the visibility of the different column menus will be very useful in scenarios when we want to create a customized column menu that contains a component with a popup. With the current implementation of the component, if we for example add a DatePicker to the column menu, the opening of the DatePicker's calendar triggers the closing of the column menu. Having a prop that controls the visibility of the column menu we can easily handle the described scenario.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
https://codesandbox.io/p/sandbox/beautiful-tristan-5nvvfy?file=%2Fpackage.json
open the console and click the export button.
Expected behavior
No error in console
Describe the bug
When exporting the Kendo UI for Vue Native Grid data to a PDF file and the paper-size property is set to true, if there are locked columns inside the Grid, these columns are exported as empty columns.
To Reproduce
Expected behavior
All Grid columns should be correctly visualized in the exported PDF file, no matter if they are locked or unlocked.
Additional context
If we set the paper-size to a pre-defined value like 'A4', the issue is not replicable