(question)
Let's say the customer is using TinyMCE 7.0 with this integration. They set the editor to be disabled disabled=true. (This will cause the editor to initially be in readonly mode) They've decided to bump the version of the integration so that it'll include this change.

Will the editor be in readonly mode?

I think it won't. Because initially editor's init method has

readonly: false,
disabled: true

but the disabled property is ignored by TinyMCE 7.0.

We can't use the isDisabledOptionSupported method without the editor instance, so it'll be tricky to set the init object correctly. (That's why I was forced to compare the versions in my PR :( )

(question) Let's say the customer is using TinyMCE 7.0 with this integration. They set the editor to be disabled disabled=true. (This will cause the editor to initially be in readonly mode) They've decided to bump the version of the integration so that it'll include this change.

Will the editor be in readonly mode?

I think it won't. Because initially editor's init method has

readonly: false,
disabled: true

but the disabled property is ignored by TinyMCE 7.0.

We can't use the isDisabledOptionSupported method without the editor instance, so it'll be tricky to set the init object correctly. (That's why I was forced to compare the versions in my PR :( )

don't we would have the same behavior using the version check? if the disabled prop will not be upgraded they will get a different behavior

(question) Let's say the customer is using TinyMCE 7.0 with this integration. They set the editor to be disabled disabled=true. (This will cause the editor to initially be in readonly mode) They've decided to bump the version of the integration so that it'll include this change.
Will the editor be in readonly mode?
I think it won't. Because initially editor's init method has

readonly: false,
disabled: true

but the disabled property is ignored by TinyMCE 7.0.
We can't use the isDisabledOptionSupported method without the editor instance, so it'll be tricky to set the init object correctly. (That's why I was forced to compare the versions in my PR :( )

don't we would have the same behavior using the version check? if the disabled prop will not be upgraded they will get a different behavior

Yes it would. Therefore we should set the init object correctly

{
...(isDisabledOptionSupported() ? { disabled: disabled, readonly: readonly } : { readonly: disabled }  )
}

(question) Let's say the customer is using TinyMCE 7.0 with this integration. They set the editor to be disabled disabled=true. (This will cause the editor to initially be in readonly mode) They've decided to bump the version of the integration so that it'll include this change.
Will the editor be in readonly mode?
I think it won't. Because initially editor's init method has

readonly: false,
disabled: true

but the disabled property is ignored by TinyMCE 7.0.
We can't use the isDisabledOptionSupported method without the editor instance, so it'll be tricky to set the init object correctly. (That's why I was forced to compare the versions in my PR :( )

don't we would have the same behavior using the version check? if the disabled prop will not be upgraded they will get a different behavior

Yes it would. Therefore we should set the init object correctly

{
...(isDisabledOptionSupported() ? { disabled: disabled, readonly: readonly } : { readonly: disabled }  )
}

isn't the same? I mean if someone with disable: true will update to a new version they will get a isDisabledOptionSupported() true and { disabled: true, readonly: false } the only difference is that if they use readonly with an old version of the editor, which is a pretty unlike scenario