Currently, the "suggest" option of the ComboBox is designed to work only in a combination with 'filter:"startswith"'. If you open this Dojo and enter "T' in the ComboBox, then focus the ComboBox out then the "Two" ComboBox item will be selected.

If in the above demo, we change the filter configuration to "contains", when we enter "T" and focus the ComboBox out, the behavior will be the same, and "Two" will be selected. If we instead of "T" enter "w" and focus the ComboBox out then "two" won't be selected. To make the "Two" item selected, with "filter:'contains'" configuration, we can use the below workaround.

No matter the below workaround, it will be very useful if the below logic or similar one can be built-in in the ComboBox component.

<input id="combobox" />
<script>
var fruit = [
    {code: 1, name: "One" },
    {code: 2, name: "Two"},
    {code: 3, name: "Three"}
];

var ds = new kendo.data.DataSource({
data: fruit
});

$("#combobox").kendoComboBox({
  dataTextField: "name",
  dataValueField: "code",
   suggest: true,
   filter: "contains",
  dataSource: ds,
  change: function(e) {
    var comboBox = $("#combobox").data("kendoComboBox");
    var dataItem = comboBox.dataItem();
    if (dataItem === undefined) {
//special code for mobile browsers to auto select the first entry
if (comboBox.text() != "") {
ds.filter({ field: "name", operator:"contains", value: comboBox.text() });
if (ds.view().length > 0) {
comboBox.select(function(dataItem) {
return dataItem.name === ds.view()[0].name;
});
}
}
    }
  }
});
</script>
<input id="fred">

A combobox that uses a grouped datasource does not adhere to WCAG 1.3.1. When a user navigates the options in the combobox popup, the group relationship is established for sighted users but the group is not announced to disabled users.

https://dojo.telerik.com/uJijOcOW/3

Bug report

Reproduction of the problem

Scenario 1 Cascade with no pre-selected values.
Dojo example: https://dojo.telerik.com/uguXisaY/4

1. Select category “Baverages”, product “Chai” and order “Cunewalde”
2. Change category to "Condiments"

Result:
In R1 2019 the change event fires in disorder (Orders, Categories and Products)
In R3 2019 the change event fires for Categories and Products
In R3 2019 SP1 the change event fires only for Categories

Scenario 2 Cascade with pre-selected values
Dojo example: https://dojo.telerik.com/uguXisaY/10

1. Select category “Condiments”

Result:
In R1 2019 the change event fires for all ComboBoxes but twice for Orders
In R3 2019 the change event fires for all ComboBoxes
In R3 2019 SP1 the change event fires for all ComboBoxes but twice for Products

Scenario 3 Cascade in Grid with no pre-selected items
Dojo example: https://dojo.telerik.com/OpOkataY/9

1. Click Edit and select "BMW" in Brand.

Result:
In R1 2019 the change event fires for all ComboBoxes in inverse order: Year, Model, Brand
In R3 2019 the change event fires only Model and Brand in this order.
In R3 2019 SP1 the change event fires only Model and Brand in this order.

Scenario 4 Cascade in Grid with pre-selected items
Dojo example: https://dojo.telerik.com/OpOkataY/10

1. Click Edit and select "BMW" in Brand.

Result:
In R1 2019 the change event fires for all ComboBoxes in inverse order: Year, Model, Brand, but fires twice for Year
In R3 2019 the change event fires for all ComboBoxes in inverse order: Year, Model, Brand
In R3 2019 SP1 the change event for all ComboBoxes in inverse order: Year, Model, Brand, but fires twice for Year

Current behavior

Expected/desired behavior

Environment

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

As per https://docs.telerik.com/kendo-ui/api/javascript/ui/combobox/events/select I am expecting that select does not fire when the user enters text but does not select an item from the list. This is consistent with your other widgets like AutoComplete.

However as seen in this dojo https://dojo.telerik.com/ESOJibEB select triggers whenever I enter text and click off the box instead of only when I click an item in the combobox.

How to reproduce:

• Open above Dojo
• Click in the combobox and type some text.
• Do not click on an item in the list and instead just click anywhere else on the page.
• Check console and you will see select has been printed.

If you need any other help, let me know.

Kind Regards,

Ben

PS Im forced to select a browser but this is the same across both chrome and firefox.

Hello, 

We have an issue with the combobox widget on chrome for android v77.0..

You can see the demo here https://dojo.telerik.com/aroMevIy.

Steps to reproduce:
1. Run the example in Dojo on chrome for android v77.0.3865.92
2. Scroll down to an item that was not initially visible and select it

The result is that nothing is selected. 
From debugging we saw that the change event on the widget is not fired.

Best regards,
Rostislav

p.s. the Additional Information Version dropdown doesn't have version 2018.1.221 as an option 

I've selected a version on which the bug is fixed!!!

Working dojo example to reproduce: https://dojo.telerik.com/aMEKuzex/2

If you set the contents of the combobox using the text() method, pressing the "X" inside the ComboBox will not fire a change event.

If you set the contents of the box using the value() method, or through the UI itself, clearing it afterwards does fire the change event, which is the expected behaviour. 

Hi,

we found a hard to reproduce bug in the combobox control. It appears infrequently while typing in the combobox input, if the combobox has grouping and the fixed header enabled. It does not seem to have functional implications to the control but it produces a javascript error.

Stacktrace:

_firstVisibleItem: function () {
    for (var t = this.element[0], n = this.content[0], i = n.scrollTop, r = e(t.children[0]).height(), o = Math.floor(i / r) || 0, a = t.children[o] || t.lastChild, s = a.offsetTop < i; a; ) if (s) {
      if (a.offsetTop + r > i || !a.nextSibling) break;
      a = a.nextSibling
    } else {
      if (a.offsetTop <= i || !a.previousSibling) break;
      a = a.previousSibling
    }
    return this._view[e(a).data('offset-index')]
  }

It seems to be a timing problem where the list is already loading again while the scroll from the item selection is not finished.

I have attached a simplified version of my app that reproduces the issue of infinite valueMapper requests.  

Reproduction steps:

1. Open the example htm file 
2. Open the browsers dev tools to the network tab and clear any request that have been logged.
3. Click "Add New Load Stop." Result: A row will added to the list view that contains a combo box and one request to the Orders endpoint will be made.
4. Set a value for the combo box that was added. Result: No additional request will be made if selecting from first few items in the list.
5. Click "Add New Load Stop." Result: A second row will be added to the list view that also contains a combo box, a query to the Orders endpoint will be made, and an infinite number of requests will be made to the ValuMapper endpoint.

This is reproducible in both Edge and Chrome browsers.

Thank you for your help,

Luke 

Hi,

You prob. already know this, but in Chrome attribute autocomplete should be "disabled" instead of "off" for e.g. combobox - then we don't get the auto fill.

Even thought it has no id nor name - I think it looks at the lavbel - in my case its "Name" and the combobox get a big Chrome auto fill from the address book. Setting it from "off" to "disabled" will disable both auto complete AND auto fill.

The same goes for the AJAX Combobox - will you notify that team too? Current hotfix for that is `$(".rcbInput").attr("autocomplete", "disabled");`

Thanks

/Anders