Bug report

`DropDownListSelectEvent.dataItem` is undefined when using keyboard to select the optionLabel, but is defined when using the mouse

Reproduction of the problem

Steps

Dojo: https://dojo.telerik.com/IvEXOvUH

Make a selection (e.g. "Apples").
Select the optionLabel item.

Expected

The value of DropDownListSelectEvent.dataItem is the same whether the selection is made via keyboard or mouse (assumedly).
The value of DropDownListSelectEvent.dataItem is clearly specified in the API docs when selecting the optionLabel.

Actual
The value of DropDownListSelectEvent.dataItem is "Select an option…" when selecting with the mouse.
The value of DropDownListSelectEvent.dataItem is undefined when selecting with the keyboard.

Environment
Kendo UI version: 2024.1.130
Browser: [all]

Hi Team, 

I would like to request to add a class which associates with the Kendo DropDownList.  This way, the developer could use CSS instead of jQuery to change the style of the specific popup.  

Thank you!

As my grid edit forms have expanded past the default popup, I have been using editable template. These are bound with MVVM and work well. But not all options work via MVVM like the cascade options below. I would like to use the cascade options in this scenario. It would be great to have all configuration options available via MVVM.

            <select id="ParentID" name="ParentID"
                    style="width: 100%"
                    data-role="dropdownlist"
                    data-text-field="Name"
                    data-value-field="ID"
                    data-cascade-from="ImprovementTargetID"
                    data-cascade-from-field="ImprovementTargetID"
                    data-cascade-from-parent-field="ID"
                    data-source="PEDropDownDataSource"
                    data-option-label="Pick PE..."
                    data-value-primitive="true"
                    data-bind="value:ParentID">
            </select>

Hi Team,

I'd like to request the functionality to add a Clear Button  for the Kendo UI DropDownList similar to the ComboBox.  

Thank you!

Add a filterOptions option that will enable users to configure attributes, placeholder, etc for the search box of the DropDownList. 

It will be very nice if the AutoComplete, DropDownList, ComboBox, and MultiSelect components have the floating label functionality like the TextBox widget 

 

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. 

I have created a new Telerk UI for ASP.NET Core R2 2018 SP1 Project and added a DropDownList Component into page.
When I use "Items" to add items manually everything is OK. but when I try to use DataSource to add Items using an Action remotely a console error is happened as "Uncaught TypeError: Cannot read property 'slice' of undefined".
JSON items is received and nothing is shown because of that error.
Please HELP

Add support for autoScroll to DropDownList options, such that the list scrolls when the mouse pointer reached the top of bottom of the container. Currently, autoScroll: true has no effect on that component. 

Mouse wheel scrolling of the options is not obvious to users, causing some to miss options that overflow the container.

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

I'm using your demo to reproduce the issue.  

When the user enters a value into the categories and tabs, the focus is not placed in the products field, instead it goes to the View Order button.  This makes using the cascade "feature" very difficult for users.  The focus should go products so they can further refine the search.  And then finally to orders.  But each time they tab they have to move the cursor back to the next field.

Also, since the product and order fields are disabled it prevents user from entering data (even if they know the correct value).  Is there a way to leave the cascade functionality whilst leaving the "child" fields enabled?  We were using it in a Region, Country, City filter, but because of these issues we have had to remove the cascade.

Expected behavior would be to leave all the fields enabled, if the user selects a category, then the subsequent fields (products and orders would be filtered to the selection) so that when the user starts typing in those the parent filter is added to their filter.

Whilst we are discussing filters, why if the filter is narrowed to a single item is it not automatically selected?  Currently the user has to filter, then select the item and then tab.  We have had numerous "bug" reports raised because the user didn't select before tabbing even though the item is the only one in the drop-down and appears to be selected.

Similarly the Mutliselect filter allows typing values, and even when the user selects the value in the dropdown and is added to the selected list, the typed text remains, making the mutliselect field value invalid on submission. 

Repro:

Open page: CascadeComboBox
Move focus to Categories combo (i used my mouse)
Type 'p' which opens the combo and shows 3 items starting with p
Select 'Products' using the down arrow (field now displays Products)
Click Tab
Focus moved to View Order button and NOT Products field.
Using the mouse to select a value works fine, but our users don't want to have to use the mouse as this slows down data entry.

I want dropdownlist to have group by with 2 fields

Currently the data-* attributes on the <option> tags are removed by the kendoDropDownList widget.
Please pass them through so they can be used.

After searching the kendo.all.js I found that there is currently no way the custom data-* can be added into the generated html code.

I'm using MVVM for a rather large SPA. Some parts of the SPA is generated on the server (webservice) which is just a partial html. Which looks like (simplest one):
<select data-role="dropdownlist" name="ProductTypeID" class="k-textbox">
	<option value="9" data-cond="DependsValue(ProductTypeCategoryID,1)">Compliments cards</option>
	<option value="1" data-cond="DependsValue(ProductTypeCategoryID,1)">Flyers</option>
	<option value="3" data-cond="DependsValue(ProductTypeCategoryID,3)">Brochures</option>
	<option value="25" data-cond="DependsValue(ProductTypeCategoryID,6)">Roll-up banners</option>
</select>

In this case the data-cond is an attribute in which there is a (javascript) function that should be run to determine if this option is valid or not (it is made hidden if not).

I was trying to convert this into a datasource which can be bound to the dropdownlist, but this has several drawbacks. The most important are:

- There are almost 60 different of these kind of dropdowns that can be generated from the server; This means a lot of extra code and webservices.

- Calling the webservice for each of them is way to slow since each field changes conditional values of other fields, and so the server would be called way to often. But on the client side this runs way faster. Even in javascript.

- The data-* attributes should be supported accordingly the html5 standard to my humble opinion :)

I found two questions regarding this, but both where unanswered.

I add them here for you comfort :)

http://www.telerik.com/forums/converting-standard-select-element-to-kendodropdownlist-removes-additional-properties-from-option-such-as-data-

http://www.telerik.com/forums/how-to-access-data--attributes-in-a-option-after-converting-select-to-a-dropdownlist

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.

The combobox currently doesn't react on the disabled-attribute for options. It should be possible to make single options visible but not selectable with this attribute as in original html-select:
http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_option_disabled
I found no way to do this yet.

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). 

Need to add configuration to display value which is combination of two or more properties or fields in dataSource. Just like valueTemplate in dropdownlist list but without html tags, like

$('#comboboxinput').kendoComboBox({
    dataSource:[{Name:"English (US)", Value:"en-US"}, {{Name:" Japanese (Japan)", Value:"ja-JP"}}],
    template:"<div>#=data.Name+' - '+data.Value#</div>"
    complexValueFormat:"data.Name+' - '+data.Value"
})

I was working on a project where I was asked to display large number of items on dropdown list so i was using template and valueTemplate confugurations, since the items was too large to scroll we decided to use combobox but the problem is unable to display complex values after selecting an item. Currently I'm looping through all items and adding a property DisplayName to each item before setting dataSource. This feature will be very useful and replace dropdownlist if dataSource is too large and complex value is to be displayed.