If used with reactive Forms, disabled property can run into "changed after checked" errors

What is the current behavior? If the Editor is used with reactive Forms together with the disabled property. It can happen, that the disabled state is not correctly processed at the editor, if the value changed during editor initialization. There is also a warning logged at console.

minimal demo codesandbox.io

What is the expected behavior? Maybe it is possible to support the disabled property at FormControl, like it is stated at the warning new FormControl({value: 'some Text', disabled: true}, Validators.required)

Which versions of TinyMCE/TinyMCE-Angular, and which browser / OS are affected by this issue? TinyMCE 5.2.0 TinyMCE-Angular 3.3.1 Chrome Browser

[jscasca]

@liesahead feel free to open a PR at any time if you can help with this issue. Unfortunately, I haven’t been able to look into it.

[LHBruneton-C2C]

It’s a really large file, but regarding tinymce, here’s what I have :

"@tinymce/tinymce-angular": {
      "version": "4.2.0",
      "resolved": "https://registry.npmjs.org/@tinymce/tinymce-angular/-/tinymce-angular-4.2.0.tgz",
      "integrity": "sha512-/idOKItFVUvxilCrTi36x6MI7r/4YuSr77fkg4efPSu7t2u1SADIfLTSF1K1RB+3ZUvy8zWB2v5kqbgD4FchNQ==",
      "requires": {
        "tslib": "^1.10.0"
      },
      "dependencies": {
        "tslib": {
          "version": "1.14.1",
          "resolved": "https://registry.npmjs.org/tslib/-/tslib-1.14.1.tgz",
          "integrity": "sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg=="
        }
      }
    },

"tinymce": {
      "version": "5.6.1",
      "resolved": "https://registry.npmjs.org/tinymce/-/tinymce-5.6.1.tgz",
      "integrity": "sha512-gLtuSk3VH5P36wYOxrkjKvLnPnuNRZ77t2fjTMz95ASnd5FsTBCLadnr8YKcWrBommFQoSzmVlTDyR7gXgR3nw=="
    },

I don’t know how package-lock.json is build. Maybe it depends on npm version.