Unplanned
Last Updated: 03 Dec 2020 13:46 by Deepak Subhedar

Bug report

Pressing the Capslock button when the ComboBox is focused triggers the opening of its dropdown list. The dropdown list opens one time when the Capslock is pressed.

  • The reported behavior was reproduced on Google Chrome and Firefox. On IE, the issue is not replicable.

Reproduction of the problem

  1. Open this Dojo and run it
  2. Select the first ComboBox with a mouse click or the "Tab" button
  3. Press the Capslock button.

Current behavior

The dropdown list of the ComboBox opens when the Capslock is pressed

Expected/desired behavior

The dropdown list of the ComboBox should not open when the Campslock button is pressed

Environment

  • Kendo UI version: 2020.3.1118
  • jQuery version: x.y
  • Browser: [Chrome 87.0.4280.88 | Firefox 78.5.0esr ]
Unplanned
Last Updated: 03 Nov 2020 10:34 by Ilia
Created by: Ilia
Comments: 0
Category: ComboBox
Type: Bug Report
0

Bug report

Reproduction of the problem

Dojo example.

  1. Press the "reset" button.

Current behavior

The ComboBox's value is cleared and the placeholder is displayed.

The Pickers had the same behavior before this issue was closed: #4767

Scenario: 2.

  1. Open the dropdown and select a different item.
  2. Click "reset". The initial item is properly displayed as selected. (expected)
  3. Click "reset" again. The value is cleared (not expected)

Expected/desired behavior

The initial value remains.

Environment

  • Kendo UI version: 2020.3.1021
  • jQuery version: x.y
  • Browser: [all]
Unplanned
Last Updated: 16 Oct 2020 09:54 by Ilia

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]
Unplanned
Last Updated: 09 Oct 2020 13:00 by ADMIN

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
});

Unplanned
Last Updated: 28 Aug 2020 11:31 by Ilia

Bug report

When using jQuery v3.5.1 and using the arrows to navigate through items in virtualized ComboBox a previous item is selected when valueMapper function is called. The behavior is not observed when using jQuery v1.12.3

Reproduction of the problem

  1. Run this dojo
  2. Click on the arrow to open the list of items
  3. Navigate through the items using the down arrow key

Current behavior

When the valueMapper function is called the selection moves to the previous item in the list

Expected/desired behavior

Selection should not change when the valueMapper function is called.
Working example with jQuery v1.12.3

Environment

  • Kendo UI version: 2020.2.617
  • jQuery version: 3.5.1
  • Browser: [all]
Won't Fix
Last Updated: 31 Jul 2020 10:32 by Anna
Created by: Anna
Comments: 4
Category: ComboBox
Type: Bug Report
0

I'm using the default theme:  "@progress/kendo-theme-default": "4.18.2" with some custom overrides.

The generated CSS has the following incorrect rule (because of the unitless zero, see https://www.w3.org/TR/css3-values/#calc-type-checking ):


.k-combobox .k-dropdown-wrap .k-clear-value {
	calc( calc( 1.2em + 8px) + 0 + 6px)
}

This rules comes from the following scss:

$picker-icon-offset: calc( #{$picker-select-calc-size} + #{$picker-select-border-width}  + #{$input-icon-offset}) !default; 

The unitless zero comes from this value:

$picker-select-border-width: 0 !default;

As a result, the "X" in a combobox overlaps the value.

 

 

Completed
Last Updated: 16 Mar 2020 08:35 by ADMIN
Release 2020.R2

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 ]
Unplanned
Last Updated: 02 Dec 2019 08:14 by ADMIN

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.

Unplanned
Last Updated: 27 Nov 2019 09:56 by ADMIN
Created by: Anders Mad.
Comments: 1
Category: ComboBox
Type: Bug Report
1

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

Unplanned
Last Updated: 11 Nov 2019 12:00 by Brent
Bug report
When submitting a selection in the ComboBox via Enter keypress an incorrect item is selected.

Reproduction of the problem
Run this dojo
Enter 199 in the input field and:
Click outside of the input field - text() returns 199, value() returns 199
Hit Tab key - text() returns 199, value() returns 199
Hit Enter key - text() returns 4, value() returns 199
With Kendo UI versions after 2018.2.516 pressing the Tab key outputs the same result as pressing the Enter key.

Current behavior
An incorrect item from dataSource is being selected on Enter keypress.

Expected/desired behavior
Selection modes should return same item.

Environment
Kendo UI version: 2018.2.516
Browser: [all]
Completed
Last Updated: 21 Oct 2019 10:21 by ADMIN

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 

 

Declined
Last Updated: 03 Oct 2019 07:28 by ADMIN

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!!!

Completed
Last Updated: 26 Sep 2019 11:32 by ADMIN
Release 2019.R3.SP1

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. 

Unplanned
Last Updated: 05 Sep 2019 10:39 by ADMIN

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.