Hi,

I think i discovered a bug caused from the workaround #84

I have a form with few form fields. Some form fields have a subscription on their valueChanges-Event. If this value changes, we reset other fields.

Now the problem is, when the form is disabled by the disabled-attribute (or by this.formGroup.disable({ emitEvent: false });) as default, the valueChanges-Event from above triggers directly on opening the component.

Example:

public ngOnInit(): void {
    super.ngOnInit();

    this.formGroupControls.someField.valueChanges.subscribe(() => this.resetOtherField());

    if (this.formModel.isReadonly) {
      this.formGroup.disable(); // Passing { emitEvent: false } makes no difference 
    }
  }

After just opening this form (component) the someField subscription triggers and therefore resets the otherField.

Even with [disabled]="this.formModel.isReadonly" instead of

if (this.formModel.isReadonly) {
      this.formGroup.disable(); // Passing { emitEvent: false } makes no difference 
    }

the valueChanges triggers. But the form was not changed at all.

Using v3.0.5 there is no problem, but using > v3.0.6 causes this problem.

I don't find a way to fix this problem by myself, so i created this issue.

Maybe you have tips or a fix for this issue.

Cheers! :-)