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
});
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.
The selections made are not displayed when the page is restored from the Back-Forward Cache
The selections made should be displayed when the page is restored from the Back-Forward Cache
Dojo example.
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.
The initial value remains.
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 dropdown list of the ComboBox opens when the Capslock is pressed
The dropdown list of the ComboBox should not open when the Campslock button is pressed
ComboBox with HighlightFirst set to false causes the widget to lose its value when navigating to it.
On the second tab navigation to the component, its value is lost and is now equal to the text.
The value of the ComboBox should be preserved.
Regression introduced in R1 2020 SP1. Related to #5400
Dojo example.
2 requests are sent to the "read" end point.
1 request is sent to the "read" end point. Note that if the input is cleared with the "clear" button, it works as expected and only 1 request is sent.
When a ComboBox is disabled, if the user tries to select the value by double click, additional new line is added to the selection
In the Demos a new line is added before the value of the ComboBox. When the same Demo is opened in a Dojo, a part from the text above the ComboBox is also highlighted. (screencast)
Only the text in ComboBox should be selected even if the widget is disabled.
The element holding the down arrow icon could be hidden when the ComboBox is disabled. - Dojo
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.
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.
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.
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
When the valueMapper function is called the selection moves to the previous item in the list
Selection should not change when the valueMapper function is called.
Working example with jQuery v1.12.3