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 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.
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
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.
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.
An error occurs when filtering the MultiSelect with grouping enabled.
An error occurs on the browser console.
No errors should occur when filtering the component.
The documentation for the Kendo UI MultiSelect widget states that the user can highlight the next/previous item using RIGHT/LEFT when the selection popup is closed. This works as expected. However, if the user then presses TAB and moves the focus somewhere else, the item remains highlighted.
Since the highlight only indicates that certain actions can be executed on the item, it should be removed in such a case as the actions are no longer executable. This can easily be reproduced with the keyboard navigation sample:
Hello!
Firstly, in the keyboard navigation demo for the MultiSelect widget (https://demos.telerik.com/kendo-ui/multiselect/keyboard-navigation) the follwing two keyboard shortcuts are documented:
In the following scenario, these shortcuts cause some strange behaviour:
I would expect "X-Large" and "2X-Large" to be selected in addition to the already selected items "Small" and "Medium". Instead, "Large" is selected as well. Is this behaviour intended?
Secondly, every time the user clicks and selects an entry of the MultiSelect popup, the popup is closed. Is there a way to prevent that closing. Or is there a way of selecting without triggering a close event (like pressing CTRL etc.)?
Thank You!
Editor components like the pickers, textboxes, etc. use an internal <input> element while submitting to get their value from. This value shows up in form.serialize() even when no value selected/provided.
In IE 11, MultiSelect with autoClose:false does not prevent the popup from closing. The widget has to be placed at the bottom of the page, so that there is no space for the popup to open below the input field.
The popup closes when the height of the input field expands to fit tags on a new line.
The popup should remain open.
The "aria-setsize" attribute is missing when initializing a MultiSelect with default selected values in AngularJS
When initializing a MultiSelect with default values, the aria-setsize attribute is missing for these values.

The default MultiSelect values should have an aria-setsize attribute added to their selected values

Hi Kendo Team,
After updating to version 2022.1.301 we noticed that the multiselect fields would look broken in some situations.
If the text of a selected item is longer than the line, the text of the new 'chip' will break into a new line.
The chip itself though keeps its fixed height of 24px resulting in an unreadable entry. (see attached image).
This only seems to be an issue in less themes.
We managed to reproduce this behavior in a dojo: https://dojo.telerik.com/ERaQegEc
You can see that in the second field we managed to fix this by modifying the styles of k-chip:
.k-chip {
line-height: 17px;
min-height: 24px;
height: auto;
}
Thanks,
Markus
In Angular we want to lazy initiate the options of a multiselect. After angular loads the multiselect directive, the control does not react on changing the k-options variable. If I recall, it should be solved when the control supports the setOptions method, like Kendo UI Grid.
Hi,
I am running in ti issue where extended MultiSelect selects primitive values after 1st value has been selected. See image blow and attached sample to recreate issue. Please also provide feedback regarding a way to mitigate this bug.
Hi Kendo support team,
I found a bug (or at least an undesired behavior) in the Kendo Multiselect widget.
After initialization the options in the existing select seem to be rebuilt receiving the content as value attribute if it did not exist before.
During this process potentially existing double spaces are replaced with single spaces (see attached image).
If the options of that select are replaced later, they will keep double spaces.
We use the selected values to receive content from the database, which in these cases is not possible anymore.
Since the content of the database is created by our client, we can't guarantee there might not be any double spaces.
In general I think that the content of the existing options should not be modified in any way.
Thanks,
Markus
See the following dojo to reproduce the behavior: https://dojo.telerik.com/oGEcaDoN