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

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 ]

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

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]

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

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!

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

• 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