Unplanned
Last Updated: 29 May 2020 11:17 by Sid

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]
Unplanned
Last Updated: 15 May 2020 13:35 by Sid

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]
Unplanned
Last Updated: 08 May 2020 11:55 by ADMIN
Scheduled for 2020.3

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
Unplanned
Last Updated: 09 Mar 2020 12:35 by Sathya
Created by: Sathya
Comments: 0
Category: MultiSelect
Type: Bug Report
0

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]
Completed
Last Updated: 14 Feb 2020 12:33 by ADMIN

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 ]
Unplanned
Last Updated: 16 Jan 2020 10:20 by ADMIN
Created by: Joseph
Comments: 0
Category: MultiSelect
Type: Feature Request
2
Add the ability to define cascadeFrom and the possibility to cascade from another widget e.g dropdown, combobox etc. 
Unplanned
Last Updated: 15 Jan 2020 16:46 by ADMIN
Created by: David
Comments: 1
Category: MultiSelect
Type: Feature Request
1
The MultiSelect should preserve the order of selected items on a form post.
Unplanned
Last Updated: 06 Dec 2019 10:32 by ADMIN
Created by: Lala
Comments: 1
Category: MultiSelect
Type: Feature Request
5
I'd like to be able to select multiple consecutive items by SHIFT + CLICK
Declined
Last Updated: 25 Nov 2019 07:25 by ADMIN

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

Unplanned
Last Updated: 07 Nov 2019 07:44 by ADMIN
Created by: Matthew
Comments: 1
Category: MultiSelect
Type: Feature Request
1

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.

Completed
Last Updated: 22 Oct 2019 09:19 by ADMIN
Release 2019.R3.SP.next
Created by: Emily
Comments: 1
Category: MultiSelect
Type: Bug Report
1

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

Completed
Last Updated: 10 Oct 2019 06:41 by ADMIN
Release 2019.R3.SP.next

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]
Unplanned
Last Updated: 09 Oct 2019 15:24 by ADMIN
Created by: David
Comments: 1
Category: MultiSelect
Type: Feature Request
1

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.

Completed
Last Updated: 07 Oct 2019 06:15 by ADMIN
Release 2019.R3.SP.next
Created by: Rainer Goos
Comments: 2
Category: MultiSelect
Type: Bug Report
0

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

 

Unplanned
Last Updated: 26 Sep 2019 10:39 by ADMIN

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!

Unplanned
Last Updated: 25 Jun 2019 08:58 by ADMIN

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.
aria-size

Expected/desired behavior

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

Environment

  • Kendo UI version: 2019.2.619
  • jQuery version: x.y
  • Browser: [all]
Completed
Last Updated: 18 Jun 2019 10:31 by ADMIN
Release 2019.R2.SP.Next

Bug report

Reproduction of the problem

Reproducible in the demos on mobile devices or in Chrome's emulator.
Screencast.

  1. Tap over the MultiSelect input area and drag to scroll the page.

Current behavior

The dropdown opens and a js exception is thrown:

"Ignored attempt to cancel a touchend event with cancelable=false, for example because scrolling is in progress and cannot be interrupted."

Expected/desired behavior

The dropdown does not open (similarly to the way the DropDownList behaves in the same scenario).

Environment

  • Kendo UI version: 2019.2.514
  • jQuery version: x.y
  • Browser: [Mobile Chrome XX ]
Completed
Last Updated: 14 Jun 2019 14:59 by ADMIN
Created by: Eduard Töws
Comments: 1
Category: MultiSelect
Type: Bug Report
1

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

Unplanned
Last Updated: 29 Mar 2019 07:39 by ADMIN
Created by: Eduard Töws
Comments: 1
Category: MultiSelect
Type: Bug Report
1

Hello ladies and gentlemen.

In Bootstrap 4 (and Material) SASS theme the opacity setting for placeholder is missed.

Example: https://demos.telerik.com/kendo-ui/multiselect/index

My fix for Bootstrap 4 (I not known the opacity setting for Material placeholders):

.k-multiselect-wrap {
  > .k-readonly {
    opacity: 0.7;
  }
}
Best regards,
Eduard Töws
Unplanned
Last Updated: 14 Mar 2019 14:11 by ADMIN
Created by: Farukh
Comments: 1
Category: MultiSelect
Type: Bug Report
0

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

1 2