1. Feedback
  2. React
  3. 56905

Welcome to the React feedback portal. We’re happy you’re here! If you have feedback on how to improve the React, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Incorrect Binding of Value Property to MultiSelect Component

At the initial stage, the component was initiated with an empty data source and the value property set to [1]. However, this time, the assigned value property was not bound to the component since the value was not present in the dataSource. After a certain timeout, the dataSource was loaded, resulting in the component receiving its data source properly, even though the values were not updated in the component. This issue occurs in version 18.2.58. However, in the previous version, the values were set properly. At the initial stage, the value of [1] was bound to the component properly, and after a certain timeout, the corresponding ID value was bound to the component.


Working version: 18.2.57

 

Breaking version: 18.2.58

 

Breaking sample: https://stackblitz.com/edit/react-hooks-usestate-example-gx4hdb?file=index.js,package.json

 

Working sample: https://stackblitz.com/edit/react-hooks-usestate-example-gx4hdb?file=index.js,package.json


Replication steps:

  1. Default selected value is "1"​
  2. the dropdown component, clears the selected value because the datasource starts as empty
  3. data source loads (used timeout to simulate slow API)
  4. dropdown does not show selected value as "1" even though, the datasource now has record 1.