We are requesting the implementation of external source drag and drop functionality for the Kendo UI Native Vue Scheduler component (@progress/kendo-vue-scheduler). This feature enables users to drag items from an external list or container — such as a task panel or resource list — and drop them onto Scheduler time slots to create new events.
vue- ^3.5.34
@progress/kendo-vue scheduler - ^8.3.0
@progress/kendo-theme default - 14.0
@progress/kendo licensing- latest
It would be beneficial for Kendo UI for Vue Grid columns to provide a built-in option for text truncation with ellipsis and an optional tooltip for overflow content
Like below dropdown tree, AutoComplete also need to support tree view.
If we use dropdown tree, it's extra step to search or filter, so we add a feature of tree view for AutoComplete is good.
A dedicated column picker would be far more intuitive: its discoverability is higher, and features like the indeterminate ‘select all’ checkbox and instant search align with the law of approximation.
For our users handling large datasets, this makes for a much faster, more cohesive tool.
1. You have documentation, eg at https://www.telerik.com/kendo-vue-ui/components/charts/sparkline
2. Type "sparkline" into the search box on your own website
3. No results are returned.
This used to work. You pushed a change which broke your site's search functionality.
Describe the bug
The rowReorder event is missing in the Wrapper Grid component, while it is available in the Kendo UI for jQuery Grid. Currently, the only way the event can be used is by using a code like the below in the mounted hook of the Vue app:
var grid = this.$refs.grid.kendoWidget();
grid.bind('rowReorder', function (e) {
console.log('row', e);
});
Expected behavior
The rowReorder event should be available for usage as the other events of the Wrapper Grid
Currently in Vue we don't provide the ability to share with the customers the source code before the compilation but just the already compiled code.
We need to provide the ability to fork the repository and build components from the Vue repository similarly to the way it is done in Angular and React.
I am using Kendo Vue Wrapper Grid that is editable. I am using the propery
:editable-create-at="bottom"
but the new rows are always added at the top.
There is another open issue related to this.
https://github.com/telerik/kendo-ui-core/issues/5198
Please provide a fix.
Describe the bug
The value of the data-grid-row-index attribute of the different Native Grid rows is always -1, no matter the scenario in which the component is used.
To Reproduce
Expected behavior
The different rows inside the Grid should have different values for the data-grid-row-index attribute.
Describe the bug
With the current Upload implementation, the component doesn't provide an option to filter the files that are selected for upload if the auto-upload property is set to true.
Currently, the files can be filtered only if the auto-upload is set to false as in this StackBlitz example.
To Reproduce
Expected behavior
The file with the letter "g" should not be uploaded
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
The package.json file of the @progress/kendo-vue-listbox package doesn't have the following definition:
"exports": {
"node": "./dist/esm/main.js",
"import": "./dist/es/main.js",
"require": "./dist/npm/main.js",
"default": "./dist/npm/main.js"
}
To Reproduce
Expected behavior
The package.json file of the @progress/kendo-vue-listbox package should have the described above definition.
Describe the bug
The following Stepper StepProps should not be required ones:
The current implementation of the Stepper's Steps requires the definition of the above properties which results to an error in a Typescript context.
Expected behavior
The listed properties should be made optional.
When using both filtering and virtualized dropdownlist, it can sometimes occur that the list will show no items after a series of repro steps:
Stackblitz (modified with only a console.log in the handlePageChange function) from Vue Dropdowns Library & DropDownList Component - Virtualization - Kendo UI for Vue Docs & Demos (telerik.com)
Describe the bug
DropdownTree component throws an error when user opens dropdown menu when they selected an item already, if valueRender prop is configured.
To Reproduce
Steps to reproduce the behavior: