Completed
Last Updated: 16 Mar 2020 10:08 by ADMIN

Bug report

The change event is being triggered when having an initially selected item in the DropDownList and then open the DropDownList and click on the default selected item. This bug is represented only in MVVM.

Reproduction of the problem

  1. Open this Dojo and run it. The three cascading DropDownLists will have default selected items
  2. Click on the first DropDownList and select the already selected "Confections" option
  3. The other two DropDownLists will be reset because of the change event thrown in the first DropDownList

Current behavior

The change event of a DropDownList with initial data selected is being triggered when clicking on the already selected value.

Expected/desired behavior

Selecting the already selected item of a DropDownList shouldn't trigger its change event because there is no actual change in the component's value. Please check this Dojo for the expected behavior.

Environment

  • Kendo UI version: 2019.2.619
  • jQuery version: x.y
  • Browser: [all]
Completed
Last Updated: 09 Mar 2020 14:02 by ADMIN
Release 2020.R2

In the DropDownList and ComboBox, virtualization only works when the popup is open. In both widgets, item navigation is functional by pressing down to select the next item in the list without opening the popup. However, when the end of the first page of results is reached, the selection goes back to the top of the first page of results instead of loading the second page via virtualization. This misleads the user in that it only presents a portion of the options available. This is also an issue for disabled users and accessibility.

https://demos.telerik.com/kendo-ui/dropdownlist/virtualization

https://demos.telerik.com/kendo-ui/combobox/virtualization

In both examples, holding down without opening the popup will never load more results.

We have had this issue in the past but it is a bigger issue now that we are focusing more on accessibility since users rely more heavily on keyboard navigation.

Completed
Last Updated: 29 Jan 2019 08:42 by Dimitar

The "change" event on DropDownList is being triggered when the value change of the widget is via API and not triggered by user interaction.

Steps to reproduce:

https://dojo.telerik.com/oKeBEZUN

  1. Manually select a value for category (like Category 4); a console item should be written for user change
  2. Click the "change doc to empty" button which clears the category
  3. Click the "change doc to values" button which programmatically sets the category

Expected: a log item is NOT added because the change was programmatic and the log item is triggered on "change"
Actual: a log item is added even though the value change was programmatic

The change detection inside the select widget is faulty in that it seems to be effected by focus/blur state.

This issue was found after upgrading kendo UI.  I believe the issue was introduced in 2018.1.117

Completed
Last Updated: 11 Jun 2019 13:23 by ADMIN
Release 2019.R2.SP.Next
Hello Patrick,

Thank you for your feedback. I managed to reproduce the scenario in this Dojo example. The current behavior looks like a bug. Therefore I have converted this thread to a Bug report in our Feedback portal. I also provide you a link with the issue to our public GitHub repository where you can also find further information on the matter. Until the bug is fixed, I would recommend you not to use 0 as grouping criteria in you project.

I also updated your Telerik Points as a thank you for your feedback.

Regards,
Veselin Tsvetanov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.