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.
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
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.
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.
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:
In the MultiSelect widget preventing the default of the filtering event while minLength is set to more than 1 causes the value method to not be able to properly get and set values of the selected dataItems.
The Clear Value button is able to clear the selected values but is not updating to visualize the change in the Widget
The button Clear Value is expected to clear the selected values and visualize the change
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.
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
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
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.
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.