You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
A dynamic section of mat-selects display wrong values when values are saved in an array. When a value is selected in the last mat-select (mat-select in last row) of the section a new row with a mat-select appears and displays the same value as the previous mat-select. This indicates they have the same value. However, the array saves the values of the mat-selects correctly, which indicates that it is a display issue.
wagnermaciel
added
area: material/select
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
P4
A relatively minor issue that is not relevant to core functions
and removed
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
labels
Aug 19, 2022
Seems like a real issue, but having mat-select in an ngFor seems pretty edge-casey, and there's an easy workaround so I'll leave this as p4. If we find more people throwing the mat-select inside an ngFor we can revisit this
Here's a workaround that ensures the "null" select gets the memo when the update happens 👍🏽
Is this a regression?
The previous version in which this bug was not present was
No response
Description
A dynamic section of mat-selects display wrong values when values are saved in an array. When a value is selected in the last mat-select (mat-select in last row) of the section a new row with a mat-select appears and displays the same value as the previous mat-select. This indicates they have the same value. However, the array saves the values of the mat-selects correctly, which indicates that it is a display issue.
Reproduction
Steps to reproduce:
Expected Behavior
If an option is chosen the newly added mat-select should not have an option displayed as seen in the image below:
Actual Behavior
If an option is chosen the newly added mat-select displays the exact same option as the previous one as seen in the image below:
Environment
The text was updated successfully, but these errors were encountered: