Bug report

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

Reproduction of the problem

1. Open the Server Filtering Demo - https://demos.telerik.com/kendo-ui/multiselect/serverfiltering
2. Open the DevTools network tab and type some text to filter the data, e.g. "Cha"
3. Select an item from the filtered data and blur the input - a read request occurs that returns the entire data.
4. Open the MultiSelect again - the same read request with the same data occurs.

Current behavior

Duplicated read request occurs when you blur and reopen the MultiSelect

Expected/desired behavior

No duplicated read requests should occur.

Environment

• Kendo UI version: 2022.3.1109
• Browser: [all]

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.

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.

Bug report

Setting the delay option of the MultiSelect doesn't have an effect.

Regression introduced with 2024.1.130

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/oyaHULOv/4
2. Type some text to filter the data

Current behavior

The 1 second delay is not respected and the data is filtered instantly

Expected/desired behavior

There should be 1 second delay before the data is filtered

Environment

• Kendo UI version: 2024.1.319
• Browser: [all]

Bug report

When the MultiSelect is created from a predefined HTML, the dataTextField and dataValueField options default to "text" and "value" instead of empty string.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/inUYekiL/10
2. Check the MultiSelect options in the browser console.

Current behavior

The dataTextField and dataValueField options default to text and value

Expected/desired behavior

The dataTextField and dataValueField's default values should be empty strings

Environment

• Kendo UI version: 2024.3.806
• Browser: [all]

Bug report

If the MultiSelect open event is prevented, the animation container has display:block style, blocking inputs beneath the MultiSelect

Reproduction of the problem

1. Open this example - https://dojo.telerik.com/EqOSOReM/38
2. Type something in the MultiSelect and blur, without selecting an item.
3. Focus the MultiSelect again
4. Try to focus the input beneath

Regression introduced with 2022.2.621

Workaround: manually hide the animation container - https://dojo.telerik.com/EqOSOReM/38

Current behavior

The k-animation-container has display:block style, preventing the input beneath it from being focused

Expected/desired behavior

The k-animation-container should have display:none style.

Environment

• Kendo UI version: 2023.1.117
• Browser: [all]

Bug report

When MultiSelect is used inside Grid columns filter, it is closing immediately after clicked in the MultiSelect filter input.

Reproduction of the problem

1. Open the Knowledge Base article - https://docs.telerik.com/kendo-ui/knowledge-base/multiselect-used-for-column-filtering
2. Click on the 'Name' column filter icon to open the filter popup.
3. Click in the MultiSelect input filter.

Current behavior

The filter popup is closing first time when clicked. Next time when the filter popup is opened it is not rendered properly.

Expected/desired behavior

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.

The issue is a regression introduced in 2022.1.301 with the following commit telerik/kendo@bb73744

Environment

• Kendo UI version: 2022.2.512
• Browser: [all ]

Bug report

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.

Reproduction of the problem

1. Open the Dojo example. - https://dojo.telerik.com/@NeliKondova/UCesAQen
2. Open the popup and scroll to the "Hungry Owl All-Night Grocers" item
3. Close the popup
4. Try to remove the "Hungry Owl All-Night Grocers" from the input

As the Dojo above does not use a remote valueMapper below is a sample project where a remote valueMapper method is implemented
WebApplication3.zip

Current behavior

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.

Expected/desired behavior

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.

Environment

• Kendo UI version: 2023.2.606
• Browser: [all ]

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

Hello!

Firstly, in the keyboard navigation demo for the MultiSelect widget (https://demos.telerik.com/kendo-ui/multiselect/keyboard-navigation) the follwing two keyboard shortcuts are documented:

• SHIFT + UP-ARROW: select previous item
• SHIFT + DOWN-ARROW: select next item

In the following scenario, these shortcuts cause some strange behaviour:

• select two consecutive items with SHIFT+DOWN-ARROW (e.g. "Small" and "Medium")
• use the arrow keys to move the focus further down (e.g. to "X-Large")
• press SHIFT+DOWN-ARROW again

I would expect "X-Large" and "2X-Large" to be selected in addition to the already selected items "Small" and "Medium". Instead, "Large" is selected as well. Is this behaviour intended?

Secondly, every time the user clicks and selects an entry of the MultiSelect popup, the popup is closed. Is there a way to prevent that closing. Or is there a way of selecting without triggering a close event (like pressing CTRL etc.)?

Thank You!

Bug report

Regression since R1 2018 SP1.

Reproduction of the problem

Dojo example.

1. Focus the MultiSelect

Current behavior

The value set in the dataBound event handler is replaced by the value set initially in the widget's options.

Expected/desired behavior

The widget should keep the value set after initialization (["AROUT", "BERGS"]) when focused.

Environment

• Kendo UI version: 2019.3.917
• jQuery version: x.y
• Browser: [all]

• Open the MultiSelect and add some items
• Use backspace to remove items

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 

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

https://dojo.telerik.com/AHAwETUx

Bug report

The "aria-setsize" attribute is missing when initializing a MultiSelect with default selected values in AngularJS

Reproduction of the problem

1. Open this Dojo and run it
2. Right-click on one of the initially selected items in the MultiSelect.
3. The selected DOM element will be a "li" tag
4. Select a new item in the MultiSelect and watch how the definition of the "li" tag will change
5. When selecting a third element in the MultiSelect. All the three "li" tags will receive an aria-setsize="3" tag, which wasn't presented for the default selected values

Current behavior

When initializing a MultiSelect with default values, the aria-setsize attribute is missing for these values.

Expected/desired behavior

The default MultiSelect values should have an aria-setsize attribute added to their selected values

Environment

• Kendo UI version: 2019.2.619
• jQuery version: x.y
• Browser: [all]

Bug report

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();
    }
}

Reproduction of the problem

Dojo example.

1. Open the browser's console.
2. Focus the input and type in some random text.
3. Click the button in the popup to add a new item.
4. The type of the request returned by the requestEnd event data is logged in the console.

Current behavior

The event data returns "read" as the type of the request.

Expected/desired behavior

The event data returns "create" as the type of the request.

Environment

• Kendo UI version: 2020.1.114
• jQuery version: x.y
• Browser: [Chrome XX | Firefox XX | Chromium Edge ]

Bug report

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.

Reproduction of the problem

1. Open this Dojo example.
2. Scroll to the bottom of the page.
3. Start selecting items until the tags do not fit the input field.
4. When the input's height expands, the popup closes.

Current behavior

The popup closes when the height of the input field expands to fit tags on a new line.

Expected/desired behavior

The popup should remain open.

Environment

• Kendo UI version: 2020.1.219
• Browser: [Internet Explorer 11]

Bug report

MultiSelect with virtualization scrolls automatically to the first item in the dropdown after selecting items.

Note: the issue is reproduced inconsistently.

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/oSuTUhiQ/4.
2. Scroll to e.g item 10296.
3. Start selecting all the items down.

Current behavior

At some point, the component will scroll to the top of the dropdown.

Expected/desired behavior

The component should not scroll to the top, the focus should stay on the currently selected item.

Environment

• Kendo UI version: 2020.2.513
• Browser: [all]

Bug report

MultiSelect with virtualization and tagMode: single deselects items when too many items are selected.

Reproduction of the problem

1. Download and unzip the attached project.
2. Run the project.
3. Start selecting items from the first item on.

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.

Current behavior

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.

Expected/desired behavior

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

Environment

• Kendo UI version: 2020.1.406
• Browser: [all]

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.