MultiSelect with virtualization scrolls automatically to the first item in the dropdown after selecting items.
Note: the issue is reproduced inconsistently.
At some point, the component will scroll to the top of the dropdown.
The component should not scroll to the top, the focus should stay on the currently selected item.
MultiSelect with virtualization and tagMode: single deselects items when too many items are selected.
For convenience, attached is a small video demonstrating the behavior.
Note: So far I was unable to reproduce the issue in a Dojo example when trying to replicate the configuration from the project.
At some point, the dropdown popup will scroll up, and some items that have been selected, will be deselected. Also, the single tag for the selected items will disappear.
The component should not be deselecting items, should not scroll up and the tag should not disappear.
Attachments:
Project - MultiSelectIssue.zip
Video - Kendosln_Issue.zip
When an empty array is passed to the MultiSelect's value method inside the deselect event, the item that is deselected remains selected in the MultiSelect.
The different MultiSelect items are deselected except for the "All" item.
*If the "if" statement is removed from the deselect event function in the Dojo, and only the 'e.sender.value([]);' is kept, the issue is reproducing no matter of the selected item in MultiSelect's popup.
Calling 'e.sender.value([]);' should remove all items selected in the MultiSelect.
Click on the "Clear values" button to see the expected behavior.
Reproducible in the demos on mobile devices or in Chrome's emulator.
Screencast.
The dropdown opens and a js exception is thrown:
"Ignored attempt to cancel a touchend event with cancelable=false, for example because scrolling is in progress and cannot be interrupted."
The dropdown does not open (similarly to the way the DropDownList behaves in the same scenario).
Currently, the MultiSelect input does not have a placeholder attribute in its rendering. This leads to inconsistency with the other input components such as AutoComplete and ComboBox.
Currently, the MultiSelect 'input.k-input-inner' element does not have a placeholder attribute. As a consequence, the color of the placeholder is slightly different than the rest of the input widgets.
The MultiSelect widgets should have a placeholder attribute in order to be consistent with the rest of the widgets such as AutoComplete and ComboBox
The MultiSelect is flickering several times when filtering and then selecting an item in Desktop mode on Safari.
The selected item flickers several times. (the selected item disappears and re-appears several times)
The selected item should not be flickering.
In MultiSelect when the value is set initially and the mapValueTo option is set to 'dataItem', if the user first open and close the popup, the last item can not be removed and an error 'c.select(...).done is not a function' is thrown.
As the Dojo above does not use a remote valueMapper below is a sample project where a remote valueMapper method is implemented
WebApplication3.zip
The last item can not be removed and an error 'c.select(...).done is not a function' is thrown in the browser`s console.
The other items except the last one can be removed as expected. Also, all items can be removed initially in case the popup has not been opened and scrolled to the last item from the value.
It should be possible to remove all items displayed in the MultiSelect input, even in a scenario where the popup has been opened and closed.
When the MultiSelect is used inside the Grid as a custom editor, the component gets closed on focus or when the user tries to select a second item.
The first item is correctly selected, however, the pop-up is closed every time the user clicks in the input, thus it is not possible to select a second item.
The popup should not close on focus the MultiSelect input and it should be possible to select multiple items.
The MultiSelect is not closed when the downArrow is enabled (column 'Works')
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
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.
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.
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
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.
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.
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.