Describe the bug
There is an incorrect export inside the @progress/kendo-vue-inputs package on line 39 in the @progress/kendo-vue-inputs/dist/esm/main.js file

This import fails because this file does not exist. When we change the above line to:
export * from './signature/interfaces/index.js'; everything works as expected.

A similar issue is found in the following file: @progress/kendo-vue-inputs/dist/esm/signature/Signature.js on line 145

The above should be changed to:
import { hasParent } from './utils/index.js';

Expected behavior
The described above exports should point to existing files

Describe the bug
When using the item property of the RadioGroup, the properties of each item are not passed to the template and thus a custom template with dynamic data cannot be created.

To Reproduce

1. Open this StackBlitz example and see the generated result

Expected behavior
The items defining the RadioGroup elements should be available in the template passed to the item property

Describe the bug

In a Native Editor scenario, if you open the View HTML window, the window can be closed only using the two buttons at its bottom.

To Reproduce

1. Open this StackBlitz example.
2. Click on the View HTML button.
3. Try to close the window using the "x" button in the upper right corner.

Expected behavior
The popup window should be closed when the "x" button is clicked

Describe the bug
The following JS error appears in the console when using the Insert Table tool of the Native Editor without choosing a table size to insert.

To Reproduce

1. Open this StackBlitz example
2. Click on the "Insert table" tool to open a popup
3. Click outside the popup

Expected behavior
No JS should appear when the user opens the popup of the "Insert Table" tool and doesn't select a table size in it.

Screenshots

Describe the bug
The current implementation of the Native Scheduler component is not affected by the Internationalization configurations applied to it.

To Reproduce

1. Open this Globalization Demo
2. In it, the IntlProvider is defined with a locale value of es
3. Having the above configuration, the first weekday in the Week view should be Monday, while, in the example, the first day is Sunday

Expected behavior
The Scheduler should accept both the Localization and Internationalization configurations applied to it.

Describe the bug
When we have multiple TimePickers on a page and start expanding their popups, the popups that are already expanded are not automatically closing.

To Reproduce

1. Open this StackBlitz example
2. Click on the "clock" icon of a random TimePicker to open its popup
3. Repeat step 2 over other randomly selected TimePicker

Expected behavior
The visible popup of a TimepPicker should be automatically closed when we expand the popup of another TimePicker

Screenshots

Describe the bug
Grid rowRender is triggered for every more than once in in-cell editing scenario vue 2

To Reproduce
https://codesandbox.io/s/confident-wind-50llik
1 Click on some cell
Current: RowRender is triggered for every row
Expected: RowRender is triggered only for the clicked row

Hi,

I'm trying to figure out how to persist and restore state in the native Vue grid.  Am I missing something; is this not available yet?

I found the article about doing it with the grid wrappers, but not native.

Thanks!

Describe the bug
The rowClick and rowDoubleClick events of the TreeList are not triggered or not triggered correctly.

• The rowClick event doesn't actually trigger the rowClick but the pointer click event.
• The doubleClick event doesn't trigger at all

To Reproduce

1. Open this StackBlitz example
2. Click on a randomly selected row
3. DoubleClick on a randomly selected row

Expected behavior
When one of the rowClick or doubleClick events is triggered, in the event handler

Describe the bug
A modal for selecting the editing mode of a recurring event appears on a double click over a recurring event even if the Native Scheduler is not editable.

To Reproduce

1. Open this StackBlitz example
2. Double-click on a random recurring event

Expected behavior
No popups should appear when double-clicking on an event when the Scheduler is not editable.

Screenshots

Describe the bug
The Native Scheduler allows you to create a new event without setting a title for it. When such an event is created, its delete (X) icon cannot be clicked.

The issue is replicable in scenarios with both default rendering of a custom SchedulerItem.

To Reproduce

1. Open this StackBlitz example
2. Double-click on the Scheduler to create a new event
3. Enter a value in the description field and save the new event

Expected behavior
When you try to delete the event that has no title, you should be able to do it

Workaround
Use the following CSS definition to workaround the bug:

div.k-scheduler-body > div > span.k-event-actions {
  z-index: 30000;
}

Here is a StackBlitz example demonstrating the usage of the above CSS.

Describe the bug
In a scenario where there is an Input with a required value that is not set initially, the Input has an invalid state. If we then programmatically update the value of the Input, the component continues to be invalid.

To Reproduce

1. Open this StackBlitz example
2. Wait for the value of the Input to be updated

Expected behavior
Once the Input has a value, it should become a valid one.

• A possible workaround of the issue can be applied using the valid prop of the Input. Here is a StackBlitz example demonstrating the usage of the valid prop.

Screenshots

"@progress/kendo-vue-dropdowns": "^3.5.0",

"vue": "^3.2.13",

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)

Hello there,

I am looking for a loading spinner solution to use with Vue Native Grid. I could not find something on the docs.

Is there any way I can show some kind of loading indicator while loading the data?

I am not using data source from Kendo, just basic method to populate `:data-items="items"`

Thank you!

Describe the bug

When we have a multi-level nesting in the data loaded in the Native TreeView the parent nodes that are below level0 are not displayed correctly when set as expanded.

Sample TreeView structure
|-Level0
-|-Level1
--|-Level2
---|-Level3

• The issue is replicable when the "animate" prop of the component is set to "true". If "animate" is set to "false", the TreeView is displaying all its nodes as expected.
• The issue is replicable when the processTreeViewItems method is used. If the TreeView is directly bound to an array, the component is working correctly. See this example.

To Reproduce
Steps to reproduce the behavior:

1. Open this StackBlitz project
2. See nodes "Item1.2" and "Item2.3"

Expected behavior
The "Item1.2" and "Item2.3" nodes should be expanded and their child nodes should be displayed by default as in this example.

Screenshots

Describe the bug
The position of the DropDownList's popup is not updated when the popup is opened above the component and the data items in the popup are filtered.

To Reproduce

1. Open this StackBlitz example in a new tab
2. Resize the browser's window in a way the DropDownlist is at the bottom of the visible area and click on the component to expand its popup. Because there is no space below the DropDownList, its popup should pop above the component
3. In the search box in the popup write "sm"

Expected behavior
The bottom of the popup should be constantly stuck to the DropDownList and not staying at it initial position above the compoennt.

Screenshots

• Bug report

Current behavior

https://stackblitz.com/edit/mt45fg-d8vmdm?file=src/main.vue

The popup is Not appended to the div provided

Expected behavior

The popup is appended to the div provided

Describe the bug
The appendTo and className properties of the Popup component cannot be set for the DropDowns, when configured through the popupSettngs prop.

To Reproduce

1. Open this StackBlitz example
2. Expand the DropDownList

Expected behavior
We should be able to add a className to the component's popup and control the element to which the popup will be appended to.

Describe the bug
The unit tests of a custom avatar component, which uses a Kendo UI for Vue Native Avatar are failing due to a problem with the license validation. This issue happens after upgrading the Kendo UI for Vue components from 3.5.0 to 3.5.1.

To Reproduce
Steps to reproduce the behavior:

1. Download this project and extract it
2. Run "yarn"
3. Run "yarn test"

Expected behavior
The tests should run correctly in version 3.5.1 as they used to be with version 3.5.2

Screenshots