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
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 a new item is added and the dataSource's sync method is called, the requestEnd event handler data (arg.type) returns the type of request as "read", instead of "create".
As a result the Add new item demo, does not work as expected, because it has a check for the type of the request in the requestEnd handler, and expects the request to be "create". Since the request type comes out as "read" the logic for selecting the newly added item is not executed.
In previous versions the request has been correctly identified as "create". The issue is exhibited only in the MultiSelect. The ComboBox and the DropDownList return the request as "create".
This behavior has been introduced in R3 2017. Reproducible in Chrome, Firefox and Chromium Edge. Not reproducible in IE11 and Spartan Edge.
As a workaround the addNew function can be modified as shown below:
function addNew(widgetId, value) {
var widget = $("#" + widgetId).getKendoMultiSelect();
var dataSource = widget.dataSource;
if (confirm("Are you sure?")) {
dataSource.add({
ProductID: 0,
ProductName: value
});
dataSource.one("sync", function() {
var index = dataSource.view().length - 1;
var newValue = dataSource.at(index).ProductID;
widget.value(widget.value().concat([newValue]));
});
dataSource.sync();
}
}
Dojo example.
The event data returns "read" as the type of the request.
The event data returns "create" as the type of the request.
I'd like to be able to select multiple consecutive items by SHIFT + CLICK
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
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.
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
Regression since R1 2018 SP1.
Dojo example.
The value set in the dataBound event handler is replaced by the value set initially in the widget's options.
The widget should keep the value set after initialization (["AROUT", "BERGS"]) when focused.
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.
Hi,
since the update to R3 2019 we have a issue with the multiselect component.
Whenever I set it to readonly:
$("#multiselect").data("kendoMultiSelect").readonly(true)
It is not possible to make it writable again with
$("#multiselect").data("kendoMultiSelect").readonly(false)
It stays readonly. What can I do?
BR Thomas
The bug I was talking was when setting tagMode of kendoMultiSelect to single, clicking the clear button (x at right of textbox) doesn’t trigger “deselect” event. Not sure if it’s by design. They fixed a similar bug regarding “change” event - https://github.com/telerik/kendo-ui-core/issues/4649.
Repro snippet could be found at
Result: The items that were selected, then un-selected still show as selected in the list
This can be reproduced on the latest demo page. https://demos.telerik.com/kendo-ui/multiselect/index