This problem can be easily demonstrated by looking at the page on the demonstration page, and then copying and pasting the same code into the kendo dojo.
The official demonstration page displays the buttons like so:

But the same code on the dojo displays the buttons like so:

As you can see, the demonstration page has a consistent style for all of the buttons, while the dojo page does not.
Both pages have the same classes on the icons:
The mixture of styles gives an unprofessional impression to the customer, and is preventing me from upgrading my codebase from version 2025.4.1321
For the simplest possible example, see this dojo snippet: https://dojo.telerik.com/aroNDBBv
The DropDownList's Keyboard Navigation Docs specify that the arrow keys move the highlight in the dropDownList, while Enter selects the highlighted item.
However, in reality, the arrow keys already select items. Via keyboard, it is not possible to select e.g. the third item in the list without selecting the first and the second item first (by pressing the down arrow).
E.g. the docs for Angular describe a different behavior.
If the user begins typing a word into the editor, the first character is automatically wrapped in a <p> tag.
The behavior between the browsers should be consistent. There should be no additional <p> tag.
Workaround: https://dojo.telerik.com/usTyJAmt/3
This is an enhancement request.
Wizard buttons can be modified via the activate event and replaced with a fully initialized Button, but it would be better to just offer more of the Button properties right on the wizard steps.buttons object properties. For example, the icon/image properties, fillMode, size, etc.
We noticed this issue on our client application. It is especially prominent on a slower network connection. We have a batch edit Grid (in cell editing). We clicked Add to create a new row, added data to it, double-clicked the Save Changes button, refreshed the page, and noticed we had 2 new entries instead of just 1 in the grid. We are currently using v2025.4.1111.
To make sure that it was not something isolated to our specific version / setup, I went to the Kendo grid demo site (https://demos.telerik.com/kendo-ui/grid/editing ) to try and reproduce. At the time of writing this ticket, the Kendo site used the latest version available, v2026.2.520.
The following steps reproduce the issue reliably.
When text is hihlighet in Rwad-Only Editor and the user tries to paste a text, the highlighted text dissapears.
Currently, the highlighted text dissapers
The highlighted text should not dissapear and the content of the Editor should remain unchanged.
kendo.ui.editor.Clipboard.fn.onpaste = function(){
if (this.editor.body.contentEditable === "false" || this.editor.body.contentEditable === "inherit" ) {
return;
}
}
Currently, the highlighted (selected) text dissapers.
The selected text should not dissapear and the content of the Editor should remain unchanged.
Workaround
kendo.ui.editor.Clipboard.fn.onpaste = function(){
if (this.editor.body.contentEditable === "false" || this.editor.body.contentEditable === "inherit" ) {
return;
}
}
The DatePicker widget does not focus the input element when the calendar icon is clicked. Because of that, validation errors are persisted even when the value of the input has been filled out correctly. The input needs to be manually focused and then unfocused to get rid of the validation message.
This behavior can be observed on the following demo page:
https://demos.telerik.com/kendo-ui/validator/custom-validation
The demo should be viewed in mobile mode.
The dropDownList supports several keyboard shortcuts as documented in https://demos.telerik.com/kendo-ui/dropdownlist/keyboard-navigation. However, when e.g. a KeyDown event is triggered (and handled) by the widget, its propagation is not stopped. This behavior can be witnessed in this DOJO.
In our case, we e.g. use dropDownLists inside dialog windows that can be closed via ESC. When pressing ESC while a dropDownList is focused, this not only closes the dropDownList (as expected), but also closes the dialog.
The dropDownList should stop the propagation of events that it handled.
Bug report
`DropDownListSelectEvent.dataItem` is undefined when using keyboard to select the optionLabel, but is defined when using the mouse
Reproduction of the problem
Steps
Dojo: https://dojo.telerik.com/IvEXOvUH
Make a selection (e.g. "Apples").
Select the optionLabel item.
Expected
The value of DropDownListSelectEvent.dataItem is the same whether the selection is made via keyboard or mouse (assumedly).
The value of DropDownListSelectEvent.dataItem is clearly specified in the API docs when selecting the optionLabel.
Actual
The value of DropDownListSelectEvent.dataItem is "Select an option…" when selecting with the mouse.
The value of DropDownListSelectEvent.dataItem is undefined when selecting with the keyboard.
Environment
Kendo UI version: 2024.1.130
Browser: [all]
The value of a disabled DropDownList is not announced in the below screen reader -> browser combinations:
NVDA with Chrome
JAWS with Chrome
The value is correctly announced by NVDA in Firefox.
After testing the scenario with the ComboBox, the value was correctly announced in all screen reader -> browser combinations.
The screen reader announces the disabled state of the DropDownList, but does not announce its value.
Note - the value of the regular select element below the DropDownList is announced.
The value of the disabled DropDownList should be announced in the above mentioned combinations.
The cascade event is triggered on initialization of the DropDownLists
The cascade event is triggered on initialization
The event should be triggered when the value of the "parent" DropDownList is changed.
When navigating between inputs and after using Shift+Tab for focusing on a previous input the DropdOwnList popup does not close on pressing 'Enter' key.
The popup does not close. If we directly focus the DropDownList and follow steps 6-8 the popup will close.
The DropDownList should close when pressing the 'Enter' key.
When the DropDownList is configured with autoWidth:true, each opening of the component increases the width of the popup with 1px
The width of the popup increases with each opening
The width should remain the same
When the value of the widget is set in the dataBound event handler the filtering events is fired and e.filter is undefined
The filtering event is fired a second time and the second time the e.filter is undefined.
Double-checlk if the filtering event should be fired a second time.
The e.filter and e.sender.dataSource.filter().filters[0] should return the same value.
When used in a regular HTML form, the CheckBox doesn't get reset by the Reset button.
Workaround: Consider using the Kendo Form instead of a regular HTML form.
The CheckBoxes don't reset when clicking the Reset button
The CheckBoxes should reset when clicking the Reset Button
If the ColorPicker tools in the Editor are configured to render a gradient, you cannot type in the HEX/RGB inputs.
The inputs are not selectable and you cannot type in them.
The inputs should be selectable so that you can type in them.
Bug report
Spreadsheet validation on datatype=list, values in the dropdown are parsed to numbers. Numeric strings are automatically formatted by removing the heading zero.
Reproduction of the problem
Dojo: https://dojo.telerik.com/eOOvKJxL
validation: {
dataType: "list",
showButton: true,
comparerType: "list",
from: "{ \"001\", \"002\", \"Baz item 3\" }",
allowNulls: true,
type: "reject"
} The bug is a regression, formatting is different with a 2017 version: https://dojo.telerik.com/sCvgBzBa/5
Environment
**Kendo UI version: 2025.1.211
**Browser: [all]
The complete event is triggered after each file upload if chunkSize is set.
The complete event is triggered for each file after the uploading is done.
The complete event should trigger only once when the upload process for all files is completed.
Workaround in this Dojo example
I am using the Kendo-UI Grid's resizeColumn method do change column widths programmatically (e.g., to distribute column widths by our own custom rules). I have noticed that doing so sometimes leads to unexpected results as demonstrated in this DOJO:
Assume a grid with two columns: one has a fixed size of 200px and the other has no explicit width set.
In the first example, we programmatically set the first column's width to 200px (which should not change anything since the column already is 200px wide.
grid.resizeColumn(column, 200);This works as expected.
In the second example, we programmatically set the first column's width first to 20px and then immediately to 200px. I would expect the final outcome to be the same, since the second column should compensate.
grid.resizeColumn(column, 20);
grid.resizeColumn(column, 200);However, the second column does not shrink and the overall grid grows larger instead. Doing this repeatedly causes the columns to grow larger and larger over time.
Of course, this is a simplified example and I do not call resizeColumn() twice right after each other.