Describe the bug
Then using the Native Tooltip with Icon tag or SVG, the component is displayed aside from the hovered element.

To Reproduce

1. Open this StackBlitz example
2. Hover either the Icon element or the SVG

Expected behavior
The Tooltip should appear exactly below the hovered element.

Screenshots
Icon:

SVG:

Can you please provide a native Vue Wizard Control like the JQuery one:

Demo of core features in jQuery Wizard widget | Kendo UI for jQuery (telerik.com)

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.

The PanelBar component is currently available only as a Wrapper component.

To use all the benefits provided by the Vue ecosystem, it will be very convenient if the component is available as a Native one. 

Currently, the Kendo UI for Vue suite has only a ToolTip Wrapper component.

It would be nice if we can see a native version of the component.

Add Native Splitter component to the Kendo UI for Vue Native suite

Currently, if we want to set the height of a Pie Chart, its labels are appearing outside the visible area of the component. This behavior can be seen in this StackBlitz example. 

While the Kendo UI for Angular and Kendo UI for jQuery have the autoFit property available in the seriesItems' configuration, this property is missing in the Native Vue Charts. making this property available in the Vue Charts will help in the implementation of specific Chart scenarios. 

Describe the bug
When we have a NumericTextbox with formatting set to "p1", "p3"..."pX"(percentage with X decimal numbers) the component is not working correctly when we try to manually enter a value in it.

• The issue is replicable when you select the content of the component and delete it, before entering a new value. If there is a value in the NumericTextbox and one just selects it and changes it, the issue is not replicating.
• The issue is not replicable if you use a formating of "p", without a decimal numbers definition

To Reproduce

1. Open this StackBlitz example
2. Select the value in the NumericTextbox and delete it(The NumericTextbox should be empty)
   
3. Try to enter 5.75

Expected behavior
The user should be able to manually enter a value by pressing "5" + "." + "7" + "5"

Screenshots

Currently, the Kendo UI for Vue suite has only a Scheduler Wrapper component.

It would be nice if we can see a native version of the component.

When you select a tab, the tab headers are completly redrawn. This makes it impossible to add CSS transitions and animations to the tabs. I would like to add an transition to `.k-state-active`, so on selection there is a nice transtion.

Instead of redrawing, only the necessary changes should be applied to the items, i.e. changing CSS classes.

It will be beneficial if we have an option to customize the element that appears in the Scheduler when we resize it. Here is a screenshot for more details:

Tooltip stays opened when the mouse is in and our fast and it goes through the tooltip itself. video in ticket - 1563700
https://stackblitz.com/edit/vue-cyjfhr?file=src%2FApp.vue

Bug report:
https://stackblitz.com/edit/bbuqh1?file=src/main.vue

Steps:
Focus the input, type some text and blur -

Current:
an warning is observed in the console and the types string is passed to the change event.

Expected:
an warning is observed in the console and the types string SHOULD NOT BE passed to the change event.

Describe the bug
The "ghost" element that appears when we try to resize an event in the Scheduler is missing in the Timeline and Month views. The result is that the users don't have a visual representation of what is the new size of the event they are modifying. The resizing itself is working correctly. The issue is only with the visual representation.

To Reproduce

1. Open this StackBlitz example
2. From the Views in the upper right corner select "Timeline" or "Month" view
3. Select a random event and try to resize it.

Expected behavior
An element that shows the possible new size of the event should appear like it is in the Day view, for example.

Describe the bug
In scenarios when we have a color applied to a Scheduler resource, the pre-defined color is not visualized as a background if we use the group prop. This happens when the resource is not available in the array passed to the group property. If the resource that holds a color is available in the group array, the colors are correctly displayed.

To Reproduce

1. Open this StackBlitz example
2. See the 4 events available in the view

Expected behavior
The events assigned to Room 1 should be with blue background and the events assigned to Room 2 should be with red/pink background. This should be valid for all scenarios in the Scheduler - with and without grouping.

Screenshots

All of the Vue Native component documentation assumes Vue 2. Vue 3 has a different configuration and the component names are sometimes different. Working with Vue 3 has been painful trial and error.

https://stackblitz.com/edit/gv4uwk?file=src/main.vue

Focus the initial input then press tab
the stepper is focused yet it does not change visually so we know it

expected:
There is a visual initial representation of the focused component

Describe the bug
The messages from the cldr-dates-full library are not loaded correctly in the Calendar component.
Month names in the Calendar control in Polish language should be in the nominative case.
Tooltips for the days in the calendar are in the genitive case and they are correct.

• The same issue could be replicable in other languages.

To Reproduce
Steps to reproduce the behavior:

1. Open this example.
2. See the translation of the month in the Calendar

Expected behavior
The month's name should be "listopad 2021". Instead, it is "listopada 2021". For reference, check this sample that uses the Kendo UI for jQuery suite and the messages are correct.

Screenshots

Describe the bug
The Native Editor blocks the browser when used in Vue 2. Meanwhile, the same component configuration works correctly in Vue 3.

To Reproduce

1. Open this CodeSandbox(Vue 2)
2. The project cannot be started or blocks the browser

Expected behavior
The example above should be working like in this project(Vue 3).

Describe the bug
The Native TimePicker component throws a console error when a value is passed to its steps property.

To Reproduce

1. Open this StackBlitz example
2. Click on the TimePicker to expand its popup
3. Open the browser's console

Expected behavior
There shouldn't be any Javascript errors when working with the Timepicker

Screenshots