When the MultiSelect is created from a predefined HTML, the dataTextField and dataValueField options default to "text" and "value" instead of empty string.
The dataTextField and dataValueField options default to text and value
The dataTextField and dataValueField's default values should be empty strings
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.
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:
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).
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
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.
MultiSelect e.preventDefault() does not work in change event when selecting/deselecting items with Ctrl+A or Chift+Arrow
No items should be selected as e.preventDefault()
is called in the select
event.
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.
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.
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 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.
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 "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
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
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.
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
Dojo example.
All items are selected, but the first two ("Chai and Chang") are not highlighted as selected.
All items should be selected and highlighted as selected.