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.
The change event of a DropDownList with initial data selected is being triggered when clicking on the already selected value.
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.
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.
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.
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:
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