Describe the bug
The color of the Gauge component is not reactively updated when the value passed to its pointerColor prop is updated.

To Reproduce

1. Open this StackBlitz example
2. Change the selection in the radio buttons

Expected behavior
The color of the Gauge's pointer should be changed every time the selection in the radio buttons is changed

Screenshots
Red pointer:

Green pointer:

Describe the bug
When using the GridPdfExport component for exporting Grid data to a PDF file the exporting operation fails with the following error:

• The issue is replicable only when working in Vue 2 context

To Reproduce

1. Open this CodeSandbox example
2. Click the button above the grid

Expected behavior
A system dialog should appear asking where the generated file should be saved

Describe the bug
The modal property of the Window is supposed to control if there is a layer behind the component that prevents or allows interaction with the elements that are below the Window.

Currently, there is no way to click the elements behind the Window.

• Possible workaround is demonstrated here. The workaround uses the following CSS:

.k-dialog-wrapper {
  height: initial;
  width: initial;
}

To Reproduce

1. Open this demo
2. Try to click on the "Close Window" button

Expected behavior
If the modal property is set to false, the user should be able to interact with the HTML elements behind the Window.

Describe the bug
When using the listNoDataRender prop of the Native MultiSelect component the following warning appears in the browser's console.

To Reproduce

1. Open this StackBlitz example
2. Open the browser's console

Expected behavior
No warnings or errors should appear in the dev console

Describe the bug
The is a slight bouncing of the DatePicker's popup when it is opened above the input of the component

To Reproduce

1. Open this StackBlitz example
2. Open the popup of the DatePicker

Expected behavior
The popup's opening animation should not have any bounces

Describe the bug
When setting the animation property of the Skeleton component to false there is a console warning.

To Reproduce

1. Open this StackBlitz example
2. Check the browser's console

Expected behavior
There shouldn't be any warnings or errors when using the Skeleton component

Screenshots

Describe the bug

Highlight some text in the Editor. Set a font colour other than black, then use the Underline tool.

Once underlined, the text decoration is not the same colour as the text.

To Reproduce

1. Open https://codesandbox.io/s/great-rosalind-43wdd0
2. Highlight any text
3. Change the font colour to anything other than black
4. Use the underline tool to underline the highlighted text
5. Deselect the text and the text decoration and font colour do not match.

Expected behavior

The font colour and underline colour should match.

Describe the bug
When we have an Input component that is used inside a Drawer, once the Input's text is selected, a JS error is thrown.

To Reproduce

1. Open this StackBlitz example
2. Click the "Magnifier" icon
3. Enter random text inside the Input
4. Select the text inside the Input

Expected behavior
The selection of the text inside the Input should not trigger any errors

Describe the bug
When configuring the Chart to have a Crosshairs the Tooltip that appears is not centered as it is in the other Kendo UI suites.

To Reproduce

1. Open this CodeSandbox example
2. Hover a randomly selected element in the Chart

Expected behavior
The Tooltip that appears above the vertical crosshair should be centered above the line

Screenshots

Describe the bug

After inserting an image using the "Insert Image" tool it is possible to add a hyperlink to it using the "Insert Hyperlink" tool.

If the image's dimensions are then edited by selecting the image and using the "Insert Image" tool, the hyperlink that was added no longer exists.

Before:

After:

To Reproduce

1. Open https://codesandbox.io/s/elegant-parm-l7w93g
2. Right click the image in the editor, you should see the option to open the link.
3. Select the image
4. Open the "Insert Image" tool
5. Change the width or height to another value (e.g. width -> 200px)
6. Click the insert button within the tool
7. Right click the image in the editor, you should see the option to open the link is no longer there.

Expected behaviour

The image should retain any hyperlinks that have been added even if it is resized.

Describe the bug
Combobox does not scroll to focused item

To Reproduce
https://stackblitz.com/edit/u4crwa?file=src%2Fmain.vue

Type v

Expected behavior
Volleyball is scrolled into view

Describe the bug
The Native TreeList component throws an error when used in inline add/edit mode, in the Firefox browser.

To Reproduce

1. Open this StackBlitz example in the Firefox browser.
2. Click the "Edit" button on a random row
3. Try to edit the content of the Input that appears in the Name column

Expected behavior
The Input's value should be editable and no errors should be thrown.

Screenshots

Describe the bug
Aria label can not be set in an icon only DropDownButton

To Reproduce
Inspect the button element

https://stackblitz.com/edit/gvk8hm-s2fmdf?file=src%2Fmain.vue

Expected behavior
We can set aria-label

Screenshots
The aria label can be set to some value

Workaround :
https://stackblitz.com/edit/gvk8hm-tquawk?file=src%2Fmain.vue

Describe the bug
When the AutoComplete and Button components are disabled, they are still focusable.

To Reproduce

1. Open this StackBlitz example
2. Press the Tab key to focus the DropDownList
3. Press the Tab key for a second time to focus the Button

Expected behavior
When disabled, both the DropDownList and Button should not be focusable

Describe the bug
When using a slot template inside the Grid, the content of the template should always have only one DOM element on the root level. If there are multiple elements on the root level, only the first element will be rendered.

In scenarios when we add a comment inside the slot template as a first element, the Grid recognizes it as the first element in the template and nothing will be rendered.

To Reproduce

1. Open this StackBlitz example
2. See the Unit Price column

Expected behavior
The rendering of the slot template shouldn't depend on the number of root elements inside it. The template should be rendered in scenarios with both single and multiple elements in the root.

Screenshots

Describe the bug
The Drag and Drop functionality of the ListBox doesn't work when one of its lists is empty.

To Reproduce

1. Open this StackBlitz example
2. Move all ListBox items to the column on the left
3. Try to move an item from the left column to the right one

Expected behavior
The users should be able to drag and drop the ListBox items no matter if its lists are empty or not

Describe the bug
Scheduler difference in initial events' positioning in Firefox

To Reproduce
https://stackblitz.com/edit/to5tp6-yqy5j5?file=src%2Fmain.vue,package.json
Open the example in FireFox and in Chrome
In Firefox the events starts from 9:30

Expected behavior
The event starts in 8:30 in both browsers

Describe the bug
When using a slot to define the columns in the Wrapper Grid, the result in Vue 2 and Vue 3 is different.

• In Vue 2, if we pass 2 columns to the slot, only these two columns are rendered in the component.
• In Vue 3, no matter how many columns we pass to the slot, the component renders all columns, based on the data in the datasource

To Reproduce
Check the two examples below:

• Vue 2 - https://codesandbox.io/s/jovial-hamilton-k6hfl7?file=/src/App.vue
• Vue 3 - https://codesandbox.io/s/empty-smoke-cnyz0t?file=/src/App.vue

The two examples use the same implementation but the number of columns rendered in each Grid is different

Expected behavior
The two examples should work the same way as in the Vue 2 application.

Screenshots
Vue 2:

Vue 3:

Describe the bug
In a scenario of a DropDownList with virtualization and a valuePrimitve set to true, the selected value disappears if the data in the popup is scrolled.

To Reproduce

1. Open this StackBlitz example
2. Open the popup of the DropDownList and select 'Item 5'
3. Open the DropDownList again and scroll the data down

Expected behavior
The selected value of the DropDownList should not disappear when scrolling its data.

Screenshots

Describe the bug
When set to "disabled", the underlying input field does not get the "disabled" attribute, so it's still editable. You cannot click on it since the wrapping span has pointer-events: none, but if you set a label for this input, you still can edit a disabled field, which is kinda no-go in terms of security.

Good thing: Updates to the disabled field do not fire an update event, which might be good or bad, depending on whether we consider security or UX.

To Reproduce

1. Open this CodeSandbox

Expected behavior
The input inside the Input component should have a disabled attribute.