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.

 

 

 

In the vue native grid, the inputs rendered in the filter row don't have a title or accessible name. This would make it nearly impossible for someone using a screen reader to understand what each field means. In order to comply with WCAG 4.1.2 (Name, Role, Value) please add a title and/or aria-label/labelledby attribute to these inputs. 

The jquery grid has the aria-label and title populated with the column name. I think it'd be even more useful if the label said "Filter by {columnName}".

Please add the ability to traverse and select rows in the vue native grid in order to match the functionality of the jquery grid and meet WCAG criteria 2.1.1 (Keyboard).

When using the chrome accessibility panel to inspect the filter operator button, there is no accessible name or title (hovering over the button does not give a tooltip with the name of the button).

The clear filter button does have an accessible name and title.

Please correct the filter operator button in order to meet WCAG Accessibility Standard 1.1.1 (Non-Text Content) and 4.1.2 (Name, Role, Value)

 

Situation:

Consider a standard chart with time periods on the x-axis, The most recent period is to the right. If you look at the chart with all periods visible and you zoom in, the chart zooms into the center of the chart. So the most recent period drops out to the right and the older periods to the left. 

 

Request:

Use a property to stick the most recent period to the right, even if you zoom in. Currently the chart zooms into the center. The requested behaviour would be: Keep the right (or left) border and zoom in/out to the left (or right) side. So regardless of the zoom level, the most right (or left) item is allways visible.

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.

Hi,

It is possible to display a vertical bar as highlighted in the image, which is in date and time range. This for time stamps not worked. Example for lunch, or not working due to bad weather.

 

Add the option of displaying multiple related tasks on one row in the Gantt chart.

I want to fold / unfold all groups of the Grid with one click by placing

When using native vue gird component often have to open modal windows to show details usually when a particular cell in the grid is clicked and do show modal windows have to use non-native <kendo-window> inside a vue component not happy with mixing jquery based wrappers inside a vue component and this is not ideal. I have explored using native vue popup component but it's not up there to offer what widows component is offering.

Please can a native vue component be developed that we in KendoWindow implementation?

Also, I did not find any example, where a kendo grid component is utilising a window component to open a modal window to show another detailed view of a selected cell from a gird (see an example UI of a grid).

Kind regards

Hammy Babar

 

I was looking through the documentation for the native drop down list and did not see an example for grouping like the wrapper drop down list has. https://www.telerik.com/kendo-vue-ui/components/datasource/datasource/grouping/ I would like to request a group functionality for the native drop down list.

Add Validation to the Kendo Vue native grid.

Hi Kendo.

 

We're trying to replace Vue Grid Wrapper with the new Native Grid and most things works awesome. We only have one blocking feature that isn't inplemented yet.

 

So my question is when is the footer-logics comming for the native grid. We want to show aggregates in the fixed footer and it would be awesome it is like the 'headerCellRender' function defined on the grid. We know there is a gouping aggregate, but this isn't the thing we want.

 

Is there any idea when or even if it is comming to the native grid?

 

Kind regards,

Sander

For Vue components, the v-model on a multi-combo box and every component must bind to the underlying object.
:value-primitive="false" doesn't work as per some suggestions.

v-model binding to the underlying object is a MUST HAVE, Top priority, number one with a bullet. Without it, your components are a PITA to use and my current proof of concept might end here and we won't use your components with some bigger projects coming down the line.

Hi all!.

Are your planning to create native gantt component?

Do you have a development plan?

I would really like to see the following:

- combobox with cascading,

- treeview.

Vue docs say it's incompatible with jquery, so I don't understand how I could use jquery based components.

It will be a very useful feature to be able to import an Excel file to the Grid component

Currently, in order to customize the Group Header the :cell-render prop of the Grid should be used. That, however, manages all cells (group header cells and column cells). In order to make the configuration more granular, please, provide a Group Header Template configuration option.

See ticket 1444254 for details. 

 

The scenario:

The start and end date for the widget is set during the component load and will trigger another function. It's impossible to change and capture the date range change from that point on without more coding - messy.

The behavior should be,

• select start date, select end date then fire the change event.
• Also during the date range selection, scrolling through months should not reset the date until an actual date is selected.

The implementation seems unfinished and unusable (at least for my use case)...it is really worthless as it stands for a date range utility....might as well just implement 2 calendar inputs and code for selection - I did this in another framework and it kinda sucked to do :-). This widget's expected behavior, its potential  would be a big time saver for a dev if it was coded more in the spirit of its name.