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 ]
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. 

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