I'd like to be able to select multiple consecutive items by SHIFT + CLICK
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.
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
There is no way to sort the selected items inside the MultiSelect.
It would be nice to have such functionality implemented or provide an implementation that can achieve the described functionality.
Currently, the relation between the MultiSelect input and its TagList element (the one that holds the selected items) is established with an aria-describedby attribute. That results in the screen readers to report the selection (all selected items) as one line of text which doesn't adequately describe the control or and its context. The text of each selected item is announced but it is not clear how many items are selected. Also, there is no articulation between each item text that is announced.
Consider and implement better relation/structure, so that the context of the widget (the selected items and their number) is announced clearly.
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.
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.
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).
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
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:
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
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.
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.
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.
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.
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
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.
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.