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
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.
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.
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.
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.
Similarly to the feedback listed in https://feedback.telerik.com/kendo-jquery-ui/1560733-multiselect-keyboard-events-bubble-although-already-handled#:~:text=The%20approach%20described%20in%20order%20to%20prevent%2Foverwrite%20the,well%3A%20kendo.ui.MultiSelect.fn._keydown%20%3D%20function%28e%29%20%7B%20e.preventDefault%20%28%29%20%7D%3B
I am exploring using a multiselect box within a window. If I choose to not allow the multiselect to autoClose, hitting the escape key will close the multiselect, but the event will continue to bubble up and will close the window. Ideally, the multiselect should close its panel, but the window it is embedded on should not.
One solution to this problem is to add a handler for the close event on the window, however there is currently no way to determine if the close event is being triggered by clicking the close button on the window, or from an escape character (e.userTriggered does not go far enough to differentiate). I would like the user to be able to click the close button manually to close the dialog, but not necessarily use the keyboard Escape key. See: https://docs.telerik.com/kendo-ui/api/javascript/ui/window/events/close
The following solution as mentioned in the feedback link above, can be used to stop the propagation of the Escape key globally, but this then breaks all other keyboard actions (which is bad from a usability standpoint). Is there any way to add this functionality? From looking at the source (which we have as part of our subscription), simply adding e.stopPropagation() when responding to the ESC key in the _keydown function of kendo.multiselect.js would be enough to fix this issue.
kendo.ui.MultiSelect.fn._keydown = function (e) {
if (e.which === 27) {
e.stopPropagation();
}
}
Thanks.
Hi Team,
I would like to request a built-in functionality to have the Kendo UI MultiSelect to select and deselect all items. Perhaps a checkbox or specific button within would be great.
Thank you!
Hi Team,
I would like to request being able to add new items into the MultiSelect and saving them per user.
It has become clear that while this control allows a user to add custom entries not currently in the pre-defined list, it appears they can't later be loaded, like when a user saves choices, including custom entries.
I've never seen a scenario where a user enters input into a control and later doesn't need to see what they enter (saved to a Db).
Therefore, the MultiSelect demo which allows you to add custom entries, but can't later display them represents an unrealistic scenario and I recommend at least adding a caveat to the page informing developers planning to use that feature of this limitation.
I like the MultiSelect and use it in many places, but since the custom add feature won't support common usage (later display what they type), I recommend this feature not be displayed as a demo until it's ready.
For example, it should accept as a property a string, delimited by commas, custom entries.
It would then iterate through custom entries and where it doesn't match, add them for you.
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.
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.
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 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.
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 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.
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.
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