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:

Describe the bug
When using the Auto-Resizing in combination with the Appearance size the Auto-Resizing isn't triggered again after the Appearance size has been changed. Because of this, the Native TextArea stays to 'big'. The Auto-Resizing is only triggered again when you change the value of the TextArea.

To Reproduce
Steps to reproduce the behavior:

1. Open this StackBlitz example
2. Fill in a value
3. Switch the 'Size' DropDownList value to 'Large'.
4. Switch the 'Size' DropDownlist value to 'small'.
5. Additional white space is visible below the value.
6. When changing the value the Auto-Resizing is triggered again.

Expected behavior
The TextArea should be resized automatically when changing its "size" appearance property, without the need to update the value of the component

Describe the bug
When working with the Wrapper DropDownList, if the component uses the v-model directive, there are some white spaces appearing in the popup of the component.

If the component doesn't use the v-model, the described behavior is not replicable.

To Reproduce

1. Open this StackBlitz example.
2. Select "Fish"
3. Select "Pizza"
4. Repeat steps 2 and 3 multiple times
5. See the white space in the popup

Expected behavior
No white space should appear in the popup of the DropDownList component.

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

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
When working with the DateRangePicker, if we want to change only the end date of the component, this is possible through the "end" input and not through a single calendar selection.

To Reproduce

1. Open this StackBlitz example
2. Select the END input. The Calendar will open
3. Click on a date in the Calendar
4. The selected date is being set to the "Start" value of the component.

Expected behavior
If the "End" input is focused, when we click on a date in the component's Calendar, only the "End" value should be changed.

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

Describe the bug
In scenarios when we dynamically add data to the beginning of the Grid, the component re-renders elements whose re-rendering can be skipped.

To Reproduce

1. Open this StackBlitz example
2. Click on the "add row to beginning" button

Expected behavior
The onUpdated method should not be called when adding a new row to the beginning of the Grid. Instead, if you open the browser's console, the result is that "updating..." is logged three times.

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

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.

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

Describe the bug
If we try to manually enter a value in the 'Start' input of the DateRangePicker, the entered value is applied to its 'End' input.

To Reproduce

1. Open this StackBlitz example
2. In the "Start" input select the field that holds the '5' digit. Now we can edit the day of the month for the Start date
3. Enter 8 with the keyboard

Expected behavior
The value of the "Start" input should be updated to 9/8/2018. Instead, the value of the "End" input is being changed to "9/8/2018" and the "Start" day continues to be "9/5/2018".

Screenshots

Describe the bug
The Bar Chart component renders only one column no matter the number of series passed to it. The Bar Chart renders only the first seriesitem passed to it

To Reproduce

1. Open this Dojo example and run it

Expected behavior

There should be two columns rendered for each category as in this StackBlitz example.

We have a window hidden with v show and a DatePicker in it.
When we open the DatePicker and try to hide the Window the popup of the DatePicker stays opened

example and steps in ticket - 1562574

workaround - delay the hiding of the Window with 200 ms to ahve a default hiding of the popup executed:

const toggleDialog = (e) => {
e.preventDefault();
setTimeout(() => {
if (visible.value) {
showPopup.value = false;
}
visible.value = !visible.value;
}, 200);
};

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 DateRangePicker doesn't display a correct time when the format prop is defined and the value of the component is set dynamically.

The bug is reproducing when the minutes in the copied value are a number bigger than 51.

To Reproduce

1. Open this project
2. Open the DateTimePicker popup and select random date + Time 01: 58
3. Focus on the DateTimePicker and press Ctrl + A
4. Copy the value of the first DateTimePicker
5. Focus on the second DateTimePicker and paste the copied value

Expected behavior
The value of the second DateTimePicker should be the same as the value of the first one.

Current behavior:
The minutes value in the second DateTimePicker is incorrect - it is 1:08 instead of 1:58

Screenshots

hhttps://stackblitz.com/edit/kgeavu?file=src/main.vue

the console.log is observed even when selecting other tabs.