Bug report

In DropDownList when virtualization is enabled and the value of the widget is set through the value method, the cascade event is fired twice.

Reproduction of the problem

1. Open the Dojo example.
2. Click the 'Set value' button

Current behavior

The cascade event will be triggered twice.

Expected/desired behavior

The cascade event should be triggered only once.

Environment

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

When there is no filter enabled in the DropDownList it is possible to select an item just by typing, without opening the DropDownList popup.

https://dojo.telerik.com/ELEfIZIx

It would be useful if such an option is available when the filter of the widget is configured. 

https://dojo.telerik.com/iliKAqUr

1. select "Oranges" from the dropdown
2. press "Change value to 'Bananas'" button
3. press "Sort" button
4. select "Oranges" from the dropdown

Expected: should see two events for "Changed to Oranges" but only see one
Actual: status only shows one value change event from the first selection of "Oranges"

It seems this issue was introduced with the fix for https://github.com/telerik/kendo-ui-core/issues/4496

The introduction of _oldText in the _change method of kendo.list.js has introduced a flaw in the value change detection for DropDownList

The above dojo presents a way to short-circuit the issue since it is not easy to show the _oldText issue since the index check works as a fallback.

Currently, the Virtualized DropDownList does not handle the autoWidth property, as describe in the offical client-side API documentation.

It would be beneficial if there is a way to circumvent around this limitation.

Bug report

The change event is being triggered when having an initially selected item in the DropDownList and then open the DropDownList and click on the default selected item. This bug is represented only in MVVM.

Reproduction of the problem

1. Open this Dojo and run it. The three cascading DropDownLists will have default selected items
2. Click on the first DropDownList and select the already selected "Confections" option
3. The other two DropDownLists will be reset because of the change event thrown in the first DropDownList

Current behavior

The change event of a DropDownList with initial data selected is being triggered when clicking on the already selected value.

Expected/desired behavior

Selecting the already selected item of a DropDownList shouldn't trigger its change event because there is no actual change in the component's value. Please check this Dojo for the expected behavior.

Environment

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

Bug report

When remote data is loaded in the DropDownList and the loading icon appears while loading, the down arrow icon remains visible. Thus, both icons are overlapping.

Reproduction of the problem

1. Open the Dojo
   Note: if the data loads fast and the issue does not occur, open the browser developer tools in order to hit the debugger in the requestEnd event handler

Current behavior

Both - the loading indicator and the down arrow icon appear at the same time:

Expected/desired behavior

The down arrow icon should disappear while the loading indicator is displayed.

The issue is a regression starting with the 2023 R2 (2023.2.606) version

Environment

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

When using AngularJS binding for dropdownlist options in the latest version of Kendo (2018.3.1017), the option labels are not dynamically bound to the scope/controller.  I changed one of the options to have the label {{::foo}} and set the field foo to "BAR" when initializing the scope.  When I run this code with the latest version, the literal text "{{::foo}}" is displayed for the first item of the drop down.  When I use an older version of Kendo (2018.2.516), the text "BAR" is displayed for that item.  This is a regression bug that is causing an error in our product.

Here is a testcase that illustrates the problem.  To toggle between the working and broken versions, change the CDN values.

https://dojo.telerik.com/umuqaFaT

Now autocomplete can not use to suggest email input, just like I input my name, the widget can show myname@xxx1.com, myname@xxx2.com, myname@xxx3.com like this, and the data will be only [{"email":"@xxx1.com"},{"email":"@xxx2.com"},{ "email":"@xxx3.com"}]

Currently to close the colorPicker manually, we have to do ".kendoColorPicker('close')", however the rest of the dropdowns/combos uses ".kendoPopup('close')".

It will be great to support it as well with colorPickers to allow closing of all popup elements on scroll with a uniform solution

It would be awesome to have the DropDownList automatically open upon focus and if filtering is enabled the focus/select the filter textbox.

This is great from a data entry standpoint where keyboard Navigation like Tab keys are used.

Maybe a property lag like OpenOnFocus=true

Please consider adding pagination to the multi-select dropdown and also the select all, deselect all options to appear inside the dropdown instead of below the input field.

Currently it is not possible to show the filter row until some data has been received and the dropdown is visible.

Please enhance/change the DropDownList widget so that it will be possible the enter a filter expression before any data is queried.

Related forum post: http://www.telerik.com/forums/server-filtering-how-to-not-query-data-until-filter-has-been-provided

The keyboard navigation in drop down lists is currently inconsistent based on the widget configuration.  When not filterable, the drop down allows you to type the first letter of one of the options in order to select it when the drop down is closed.  For example, tab to the drop down, do not open it, and type 'b' to select Bob. 

When the drop down is filterable, that behavior does not work.  You must use alt-down to expand the drop down and then begin filtering.  

I propose that the widget can consistently handle both cases by detecting whether the drop down is currently open in the keydown handler.  If filterable, and open, move into the filtering logic.  If filterable, and closed, stick with the standard selection logic.

The default behaviour of select elements is to open up with a space-keypress when the elemented is selected (focused). 

Users wonder why the filter has not been removed from the dropdownlist when they use a browser's text INPUT[X] to delete the filter. The browser raises no event is raised when the X is clicked, and so the list does not revert to the unfiltered list. Users must hit the Delete keys on the keyboard. Although developers can use CSS to remove the browser's [X], it would be more convenient if kendo could do this by default for the dropdownlists's filter box, so that developers would not have to remember to add the CSS every time.

If you're trying to create an accessible form, "the value of the for attribute must be the same as the value of the id attribute of the form control" [1]. Since the ComboBox widget generates a new element and hides the original select element, the for attribute no longer matches this new input element. I think it would be good if the ComboBox widget would somehow keep the for attribute of the associated label element in sync with the newly generated input element.

[1]: http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H44

ComboBox and DropDown are different because the first allows you to enter values non in list, but if you are using Cascading ComboBox, entering a value non in list in the first choice, the second choice is disabled. I'like to have cascading for values in list with option for inserting values non in list.

the multiselect control should have the possibility to define elements as not editable (readonly) so that those elements can not be removed while other elements can be removed or new elements can be added.

After updating the version of Kendo we are using to 2022.1.412 we noticed a weird behavior in the DropDownLists. Clicking the drop down arrow once opens the list, then clicking the arrow again closes and re-opens the list instead of just closing it. Note that this does not happen while clicking on any other part of the drop down to close it, selecting an item from the drop down, or clicking outside the drop down list. It only happens while clicking on the arrow button.

Behavior can be seen in the demos on these pages:

https://demos.telerik.com/kendo-ui/dropdownlist/template

https://demos.telerik.com/kendo-ui/dropdownlist/grouping

https://demos.telerik.com/kendo-ui/dropdownlist/cascadingdropdownlist

However the behavior does not appear on these pages:

https://demos.telerik.com/kendo-ui/dropdownlist/virtualization

https://demos.telerik.com/kendo-ui/dropdownlist/serverfiltering

Steps to Reproduce:

• Click the drop down arrow to open the drop down list
• Click on the arrow again and observe the list close and re-open (Note it sometimes doesn't happen right away but takes a few tries)