Setting the delay option of the MultiSelect doesn't have an effect.
Regression introduced with 2024.1.130
The 1 second delay is not respected and the data is filtered instantly
There should be 1 second delay before the data is filtered
When using the Multiselect with Javascript Api in following order:
- Disable
- Select
- Enable
The Multiselect Control is enabled, but the Items are still disabled and therefore cannot be removed by the X.
Can be reproduced in the official demo (see Screenshot): https://demos.telerik.com/kendo-ui/multiselect/api
If the MultiSelect open event is prevented, the animation container has display:block style, blocking inputs beneath the MultiSelect
Regression introduced with 2022.2.621
Workaround: manually hide the animation container - https://dojo.telerik.com/EqOSOReM/38
The k-animation-container has display:block style, preventing the input beneath it from being focused
The k-animation-container should have display:none style.
If you filter the MultiSelect and then blur it, a read request occurs that retrieves all the data. Then, if you open the MultiSelect, another read request triggers with the same data as response
Duplicated read request occurs when you blur and reopen the MultiSelect
No duplicated read requests should occur.
When MultiSelect is used inside Grid columns filter, it is closing immediately after clicked in the MultiSelect filter input.
The filter popup is closing first time when clicked. Next time when the filter popup is opened it is not rendered properly.
The filter popup should not be closed when clicking in the Multiselect filter input. The MultiSelect list items should be rendered below the filter input.
When there are items selected in the MultiSelect and the close icon is clicked the popup is opened for a moment
The popup is opened for a moment
The popup should not get opened unexpectedly.
The multiSelect supports several keyboard shortcuts as documented in https://demos.telerik.com/kendo-ui/multiselect/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 multiSelects inside dialog windows that can be closed via ESC. When pressing ESC while a multiSelect is focused and open, this not only closes the multiSelect (as expected), but also closes the dialog.
The multiSelect should stop the propagation of events that it handled.
MultiSelect doesn't focus the first suggested item of the popup
The first suggestion of the popup is not focused as expected.
The first suggestion should be focused.
Hello dear support,
I ve a strange behavior that I may qualify as bug.
I ve tried to reproduce here https://dojo.telerik.com/osEPIvOG wit a result shown in this animated gif here attached (DPSN-13445).
Basically what's happening is that if your are selecting / clearing elements that looked to be in different pages (view), the dataItems() function does not return the correct value, but some previous item.
This "bug" is always reproducible;
Please let me know if there is a bad implementation (I m using here basic Telerik sample) or if there is a workaround, or if I can expect a fix;
By advance thx for your swift reply.
Dojo example.
The filter is cleared and all the items in the dataSource are listed, even though "c" remains in the input area.
If step 2 is omitted, the filter is not cleared.
The filter should not be cleared. After step 3 the MultiSelect should still show only "Canada" in the list of items.
LS,
When the option highlightFirst is set to false and the autoBind is set to false, the first item is always highlighted.
Steps to reproduce:
Edit this example: https://demos.telerik.com/kendo-ui/multiselect/index
Add the parameters:
highlightFirst: false,
autoBind: false,
Click on the multiselect, the multiselect will open, but the first item is highlighted. Expected behaviour: first item not highlighted.
Change the autoBind to true or undefined, the first item isn't highlighted.
The problem with the first item highlighted is that this option will be selected when the user hits enter.
Is there any work around for this issue?
Thanks in advance.
Maritn Quaak
When a new item is added and the dataSource's sync method is called, the requestEnd event handler data (arg.type) returns the type of request as "read", instead of "create".
As a result the Add new item demo, does not work as expected, because it has a check for the type of the request in the requestEnd handler, and expects the request to be "create". Since the request type comes out as "read" the logic for selecting the newly added item is not executed.
In previous versions the request has been correctly identified as "create". The issue is exhibited only in the MultiSelect. The ComboBox and the DropDownList return the request as "create".
This behavior has been introduced in R3 2017. Reproducible in Chrome, Firefox and Chromium Edge. Not reproducible in IE11 and Spartan Edge.
As a workaround the addNew function can be modified as shown below:
function addNew(widgetId, value) {
var widget = $("#" + widgetId).getKendoMultiSelect();
var dataSource = widget.dataSource;
if (confirm("Are you sure?")) {
dataSource.add({
ProductID: 0,
ProductName: value
});
dataSource.one("sync", function() {
var index = dataSource.view().length - 1;
var newValue = dataSource.at(index).ProductID;
widget.value(widget.value().concat([newValue]));
});
dataSource.sync();
}
}
Dojo example.
The event data returns "read" as the type of the request.
The event data returns "create" as the type of the request.
Hi,
We are using the Kendo Multi Select widget, and it was just reported that you can't remove a tag from the list when clicking on the Close (X) icon when using Safari on iPadOS 13.1.3. I was also able to reproduce this on the multiselect demo here - https://demos.telerik.com/kendo-ui/multiselect/index. We are currently on version 2019.2.619, however I also tried it on the latest with the demo and it also didn't seem to work.
Is this a known defect?
Thanks,
Emily
Regression since R1 2018 SP1.
Dojo example.
The value set in the dataBound event handler is replaced by the value set initially in the widget's options.
The widget should keep the value set after initialization (["AROUT", "BERGS"]) when focused.
Hi,
since the update to R3 2019 we have a issue with the multiselect component.
Whenever I set it to readonly:
$("#multiselect").data("kendoMultiSelect").readonly(true)
It is not possible to make it writable again with
$("#multiselect").data("kendoMultiSelect").readonly(false)
It stays readonly. What can I do?
BR Thomas
When the MultiSelect is wrapped in a container with class .k-edit-field
or .k-edit-buttons
(e.g in a Grid popup editor) and the selected tags are hovered, their background-color becomes transparent.
The issue is partly related to #701.
The MultiSelect tags should not have transparent background when hovered.
The issue can be reproduced with the following Dojo example:
Product:
Hello ladies and gentlemen.
Readonly mode does not work correctly in Bootstrap 4 Theme.
If the MultiSelect is put into readonly mode programmatically and has a value and clearButton option is true - clear button is displayed and the value can be cleared.
https://dojo.telerik.com/UsiXAZuv
Best regards,
Eduard Töws