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 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
The @progress/kendo-ui npm package creates the following dependency tree:
@progress/kendo-ui 2026.1.415
|
- @progress/kendo-pdfviewer-common ^0.6.4 -> 0.6.4
|
- pdfjs-dist 4.6.82 -> 4.6.82
|
- canvas ^2.11.2 -> 2.11.2
|
- @mapbox/node-pre-gyp ^1.0.0 -> 1.0.11
|
- tar ^6.1.11 -> 6.2.1All packages have been updated to the latest version possible.
Versions <= 7.5.10 of tar have multiple known vulnerabilities:
Reordering in the same column is not working correctly
The task order remains the same
IT should be possible to reorder the tasks in the same column
I realize this has been covered by this workaround in the past, but the need to write extra code for moving the column back to the original position makes this seem a bit "hacky" and most importantly, the user experience of being allowed to drag the column in the first place just to see it jump back seems wrong.
The good news is that the kendoGrid already has a mechanism for preventing the columnReorder event from getting fired in the first place! The bad news is that it only happens for columns that have either of these 2 classes ["k-group-cell, "k-hierarchy-cell"]
My request is to have a configuration option that enforces that same behavior for specific columns as:
1. Add a "reorderable" flag to be set as part of the column configuration (set it to false for those we want to keep in place)
2. This flag will set a class on those columns the same way it works for columns with "k-group-cell" or "k-hierarchy-cell" classes, so the event can be prevented.
There is one important caveat to consider with this approach: Only columns at the front and the back of the grid can be locked in place, so there needs to be validation to prevent having non-reorderable columns among reorderable ones.