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 ]

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 

Bug report

In a Form that has a ComboBox among other inputs, clicking the reset button only clears the value of the ComboBox.

Regression introduced with 2024.1.319

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/@martin.tabakov@progress.com/oBORokAf/2
2. Type some text in the inputs
3. Click the reset button.

Current behavior

Only the ComboBox's value is cleared

Expected/desired behavior

All inputs' values should be cleared

Environment

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

Bug report

The ComboBox's popup is misplaced the first time it opens when configured with RTL and autoWidth:true

Regression introduced with 2024.1.130

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/iWuBAcez/6
2. Open the ComboBox

Current behavior

The popup is misplaced on the first open

Expected/desired behavior

The popup should be aligned with the input

Environment

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

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]

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]

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.

Bug report

ComboBox select() does not select after version 2021.3.914 when using a serverFiltering

Reproduction of the problem
Open the Dojo - https://dojo.telerik.com/owUfOLef/4


Expected/desired behavior
The first item shall be selected initially.

Environment
Kendo UI version: 2021.3.914 or newer
Browser: [all ]

To say that you have "Cascading ComboBox" functionality is misleading. You do have "Cascading ListBox" functionality - whereas if a value is picked in the parent listbox, the child will populate with a filtered, dependent list. Changing the parent changes the dependent items in the child list box.

However, the difference with ComboBoxes is that the user can also type a value in, if it doesn't appear in the bound dataset. While this does work as expected for the child ComboBox in the cascading example - it DOES NOT work for the parent. If you type a value into the parent, the child ComboBox remains disabled. You should be able to at least type into the child box. 

We have a simple need for a Manufacturer / Model selection in two cascading ComboBoxes. If the manufacturer does not exist, we want to be able to allow the user to type it in. Since it's a new manufacturer - there are no associated models in the bound dataset, yet. The dependent child ComboBox should at least be enabled so the user can enter the new model.

This behavior can be experienced in your online example. If you pick a value in the parent, the child refreshes and rebinds accordingly. But if you type in the parent - the child remains disabled. This is a bug, if you intend on maintaining that you have "Cascading ComboBox" functionality.

I was given a "workaround" by your support team - but there are still lingering effects (especially on reloading the form with existing data) that would not be an issue if the cascading combobox implementation was completed properly.

Bug report

When a ComboBox is disabled, if the user tries to select the value by double click, additional new line is added to the selection

Reproduction of the problem

1. Open the Api ComboBoxDemo
2. Select an item
3. Click on the 'Disable' button
4. Double click in the ComboBox to select the value
5. Paste it

Current behavior

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)

Expected/desired behavior

Only the text in ComboBox should be selected even if the widget is disabled.

Workaround

The element holding the down arrow icon could be hidden when the ComboBox is disabled. - Dojo

Environment

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

Bug report

Regression introduced in R1 2020 SP1. Related to #5400

Reproduction of the problem

Dojo example.

1. Open the browser's dev tools Network tab.
2. Run the example.
3. Type in "s" in the ComboBox. A request is sent and the popup displays matching items (expected).
4. Press Backspace key to clear the ComboBox input.

Current behavior

2 requests are sent to the "read" end point.

Expected/desired behavior

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.

Environment

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

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 ]

Bug report

ComboBox with HighlightFirst set to false causes the widget to lose its value when navigating to it.

Reproduction of the problem

1. Open this dojo example - https://dojo.telerik.com/@martin.tabakov@progress.com/aDAYULeZ/4
2. Navigate to the ComboBox with tab so that it will open, and check the console to see the value and the text.
3. Navigate once again to the ComboBox.

Current behavior

On the second tab navigation to the component, its value is lost and is now equal to the text.

Expected/desired behavior

The value of the ComboBox should be preserved.

Environment

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

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.