I'll try to add some more information about this to the docs in the next few weeks.

We have very little documentation on how disabling controls work, and given the nuances, we really should do a better job.

If you add another control to the form, the form stays enabled, and you'll see that the array value disappears as expected. And as a disabled group, its value contains all the values of its children, including disabled ones. All of the form controls inside it are disabled, so it also becomes disabled. In the plunker repro from the Github issue, the parent form is not actually enabled.

No matter what you set the value to, you'd get an empty array back.Ģ -That said, a disabled group's or array's value should never be included in its parent form's aggregate value if its parent form is enabled. Otherwise, you'd get the confusing scenario where it seems like setting the value doesn't work. So when you request a disabled array's value directly (e.g. What you set is what you get, and all values are retained on disable. This is the model for how form groups and form arrays work when disabled. tValue('Nancy')), then you will always get the same thing back when you 'get' the value (e.g. Like with native HTML forms, disabling a form control element simply disables changing the value in the UI, so you can still get and set the individual value programmatically if you like. It makes sense when you consider an individual form control. It was originally designed this way so form controls at all levels act the same way when disabled. ('arr').value) contain all the values of its children. It's expected that a disabled form group's/array's own value property (i.e. However, form groups/arrays act slightly differently when they are disabled. What is the motivation / use case for changing the behavior?ġ - When a form group or form array is enabled, it omits any disabled children from its serialized value to mimic native form behavior. Minimal reproduction of the problem with instructions I think a disabled formGroup's value should return an empty object or some other alternative. It looks like it is a 'normal' behavior from what i can see in this issue.īut I think there is an unexpected behavir which is that when I access the value of the formGroup when it is disabled, I get all the values from this group, even though all its children are disabled.īut when i only enable one, and access the formGroup value, I only get the enabled formControl's value. support request => Please do not submit support request here, instead see Ī formGroup can be invalid and valid at the same time when it is disabled. Bug report => search github for a similar issue or PR before submitting

Angular formgroup disable