Bug report

When the Chinese IME typing is used and the minLength is set in the ComboBox the items can not be properly selected using the keyboard.

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/@NeliKondova/EZILudiz
2. Add and use the Chinese language
   
3. Type 'bao' and press space to convert to Chinese
4. Press Tab or Enter to select.

Current behavior

When minLength is defined the item in the ComboBox is not selected, the dataitem is not accessible in the change event handler (screencast). The item is selected as expected if the value is copy pasted (包).

Expected/desired behavior

The items should be selected when using the Chinese IME typing after filtering the data and selecting an item through the keyboard.

Environment

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

Bug report

When the virtualization is enabled, mapValueTo option is set to dataItem and initial value is set in the ComboBox, the cursor is not set at the end of the item.

Reproduction of the problem

1. Run the Dojo
2. Open the dropdown popup.

Current behavior

The loaded value is 'Hungry Owl All-Night Grocers' but the cursor is not set at the end of the text, but at the fifth position in the item.

Expected/desired behavior

The cursor should be set at the end of the text.

Environment

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

Hi Team, 

I would like to request to include in the built-in API the functionality to hide the FixedGroupHeaderTemplate.  I like the appearance of the UI for ASP.NET AJAX RadComboBox when it is grouping, and it would be nice if the Kendo UI ComboBox could be configured to have the same look without manipulating CSS and adding extra code to the DataBound event.

Thank you!

Bug report

When making a selection, navigating to another page, and going back to the initial page, which is restored from the Back-Forward Cache in Firefox, the selection of the ComboBox is not displayed.

Reproduction of the problem

1. Go to the ComboBox demo
2. Make a selection in the ComboBoxes
3. Click on any other demo link in the navigation pane to the left (e.g. “Server Filtering”)
4. Press the "Back" browser button

Current behavior

The selections made are not displayed when the page is restored from the Back-Forward Cache

Expected/desired behavior

The selections made should be displayed when the page is restored from the Back-Forward Cache

Environment

• Kendo UI version: 2020.3.915
• Browser: [Firefox 81.0.2]

If you bind a ComboBox widget to a datasource containing arbitrary objects that contain a "data" field, the dropdown items will be "undefined" instead of the value of the dataTextField. I'm guessing the data field is messing up the template variable.

var formData = [
   {
      key: '1',
      description: 'CT Safety',
      formTypeCd: 'S',
      data: {foo: '', bar: ''}
   },
   {
      key: '2',
      description: 'MR Safety',
      formTypeCd: 'S',
      data: {foo: '', bar: ''}
   },
   {
      key: '3',
      description: 'Medicare > 60 Billing',
      formTypeCd: 'I',
      data: {}
   }
];

$("#forms-combobox").kendoComboBox({
   dataTextField: "description",
   dataValueField: "key",
   dataSource: formData
});

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

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

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.