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

Bug report

MultiSelect doesn't focus the first suggested item of the popup

Reproduction of the problem

1. Open this Dojo
2. Make sure it has at least 2 values set on initialization
3. Write some text until the popup opens with some suggestions

Current behavior

The first suggestion of the popup is not focused as expected.

Expected/desired behavior

The first suggestion should be focused.

Environment

• Kendo UI version: 2020.3.1118 or later
• Browser: [all]

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]

Bug report

When there are items selected in the MultiSelect and the close icon is clicked the popup is opened for a moment

Reproduction of the problem

1. Open the Demo - https://demos.telerik.com/kendo-ui/multiselect/index
2. Click the close icon in the first MultiSelect

Current behavior

The popup is opened for a moment

Expected/desired behavior

The popup should not get opened unexpectedly.

The issue is a regression introduced in 2022.1.412 version with the following commit - telerik/kendo@7953a90

Environment

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

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

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.

I'm submitting a...

• Bug report

Current behavior

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.

Expected behavior

The MultiSelect tags should not have transparent background when hovered.

Minimal reproduction of the problem with instructions

The issue can be reproduced with the following Dojo example:

• Hover over one of the selected tags to see the background-color issue.

Environment

Product:

• Kendo Ui for jQuery

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

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]

The multiSelect supports several keyboard shortcuts as documented in https://demos.telerik.com/kendo-ui/multiselect/keyboard-navigation. However, when e.g. a KeyDown event is triggered (and handled) by the widget, its propagation is not stopped. This behavior can be witnessed in this DOJO.

In our case, we e.g. use multiSelects inside dialog windows that can be closed via ESC. When pressing ESC while a multiSelect is focused and open, this not only closes the multiSelect (as expected), but also closes the dialog.

The multiSelect should stop the propagation of events that it handled.

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]

The documentation states that the Kendo UI MultiSelect widget' options contain a "messages" property that allows the customization of tooltips etc. In the corresponding TS typing, this property is not defined.

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

Reproduction of the problem

Dojo example.

1. Focus the MultiSelect and type in "c". The data is filtered and "Canada" is displayed in the list.
2. Select "Canada".
3. Click in the MultiSelect's input area.

Current behavior

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.

Expected/desired behavior

The filter should not be cleared. After step 3 the MultiSelect should still show only "Canada" in the list of items.

Environment

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

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

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

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]

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