Bug report

When filtering the DropDownList data when a limited amount of items remain the popup container is displayed above the DropDown element when sufficient space is available below the element

Reproduction of the problem

1. Run this dojo
2. Enter "123" - the popup container with the list of items is displayed below the DropDown element
3. Enter "1234" - the popup container with the list of items is displayed above the DropDown element when sufficient space is available below the element
4. Enter "12345" - the NoDataTemplate is displayed above the DropDown element when sufficient space is available below the element

Expected/desired behavior

The popup container with the list of items should be displayed below the DropDown element when sufficient space is available below the element

Environment

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

In the DropDownList and ComboBox, virtualization only works when the popup is open. In both widgets, item navigation is functional by pressing down to select the next item in the list without opening the popup. However, when the end of the first page of results is reached, the selection goes back to the top of the first page of results instead of loading the second page via virtualization. This misleads the user in that it only presents a portion of the options available. This is also an issue for disabled users and accessibility.

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

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

In both examples, holding down without opening the popup will never load more results.

We have had this issue in the past but it is a bigger issue now that we are focusing more on accessibility since users rely more heavily on keyboard navigation.

Hi 

I'm using  lastest version 

demo: https://dojo.telerik.com/eZOPEVeL

In offical demo i found a problem, i don't know that is a issue or any thing.

When i use DropDownList Virtualization, i filter "LILA-Supermercado" then selected a value 10780, then fire change event (that true)

Then, I open and close dropdownlist, does not choose any thing, just open and close, dropdownlist fire change event again (that not true)

this happen with any value which not loading before scroll.

some one help me

I am using a DropDownList with dynamic items that are grouped.

When opening the dropdown without items in the datasource the fixed group header is displayed empty.

When removing the last item from the datasource after the DropDown has already been opened, the first group header is still displayed when opening the dropdown.

I would expect the group header to never be displayed if there is no data.

See Dojo: https://dojo.telerik.com/EviPepIJ

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]

Hello Patrick,

Thank you for your feedback. I managed to reproduce the scenario in this Dojo example. The current behavior looks like a bug. Therefore I have converted this thread to a Bug report in our Feedback portal. I also provide you a link with the issue to our public GitHub repository where you can also find further information on the matter. Until the bug is fixed, I would recommend you not to use 0 as grouping criteria in you project.

I also updated your Telerik Points as a thank you for your feedback.

Regards,
Veselin Tsvetanov
Progress Telerik

Hello,

Drop down widget is defaulted to first option even though ng-model is undefined, in case where we bind same value to k-data-value-field and k-data-text-field.

Please have a look on the below sample code where you can find issue. My expectation is drop down should not default when model value is not assigned. 

 

Code:

                                                          

<!DOCTYPE html>
<html>
<head>
    <base href="https://demos.telerik.com/kendo-ui/dropdownlist/angular">
    <style>html { font-size: 14px; font-family: Arial, Helvetica, sans-serif; }</style>
    <title></title>
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.1.115/styles/kendo.common-material.min.css" />
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.1.115/styles/kendo.material.min.css" />
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.1.115/styles/kendo.material.mobile.min.css" />

    <script src="https://kendo.cdn.telerik.com/2019.1.115/js/jquery.min.js"></script>
    <script src="https://kendo.cdn.telerik.com/2019.1.115/js/angular.min.js"></script>
    <script src="https://kendo.cdn.telerik.com/2019.1.115/js/kendo.all.min.js"></script>


</head>
<body>
<div id="example" ng-app="KendoDemos">
    <div class="demo-section k-content" ng-controller="MyCtrl">
    <input kendo-drop-down-list
            k-data-text-field="'name'"
            ng-model="data"
            k-data-value-field="'name'"
            k-data-source="productsDataSource"
            style="width: 100%"></input>


</div>
</div>

<script>
  angular.module("KendoDemos", [ "kendo.directives" ])
      .controller("MyCtrl", function($scope){
   // $scope.data=0;
    $scope.productsDataSource = new kendo.data.DataSource({
                        data: [{
            'name':'Active','id':0

          },{'name':'Cancel','id':1}]
                    }
                );





      });
</script>


</body>
</html>

 

 

 

 

 

The "change" event on DropDownList is being triggered when the value change of the widget is via API and not triggered by user interaction.

Steps to reproduce:

https://dojo.telerik.com/oKeBEZUN

1. Manually select a value for category (like Category 4); a console item should be written for user change
2. Click the "change doc to empty" button which clears the category
3. Click the "change doc to values" button which programmatically sets the category

Expected: a log item is NOT added because the change was programmatic and the log item is triggered on "change"
Actual: a log item is added even though the value change was programmatic

The change detection inside the select widget is faulty in that it seems to be effected by focus/blur state.

This issue was found after upgrading kendo UI.  I believe the issue was introduced in 2018.1.117

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

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.