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
{{ message }}
Repository navigation
FormControlDirective and FormControlName do not call setDisabledState on ControlValueAcessor instances when the CVA is added and is enabled #35309
When you add a CVA to a form via the FormControlDirective directive or FormControlName directive with reactive forms and the CVA has implemented setDisabledState the the setDisabledState and the FormControl instance is enabled, setDisabledState is not called on the CVA instance, it is however called with the FormControl is disabled.
Reacted by Chris Shouts, Michael Marcuccio, Joe Percy, Michał Stawicki, Dylan Hunn, Liad Idan, roxfives, Clemens Heppner, stefnotch, Marvin Heilemann and 5 more
Reacted by Joe Percy, Michał Stawicki and Vlad Dumbrava
Activity
AndrewKushnir commentedon May 27, 2020
FYI this issue is potentially related to #13856.
43 remaining items
dylhunn commentedon Oct 10, 2022
Whoops, this is the issue, not the PR :)
fix(forms): call `setDisabledState` on `ControlValueAcessor` when con…
angular-automatic-lock-bot commentedon Nov 11, 2022
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.