TinyMCE as first class citizen in ACF

see: https://github.com/AdvancedCustomFields/acf/issues/906#issuecomment-2095595565
see: https://github.com/AdvancedCustomFields/acf/issues/876#issuecomment-1719231612

The entire reason we use ACF is to continue using TinyMCE in WordPress while also being able to leverage Gutenberg for some aspects.

Gutenberg solves:

• content is stored in post content -> search works
• easier to reuse blocks across multiple templates

TinyMCE solves:

• much more stable across WordPress versions
• easier for content editors

In practice we disable all core blocks and use ACF to create only that which is needed and supported by each design system.

"just use inner blocks" isn't a viable direction for us.
We don't want to use core blocks.

What frustrates me about the current situation is that ACF isn't open to community fixes.

For example the JavaScript source code isn't present in this repo (not even unminified sources: https://github.com/AdvancedCustomFields/acf/issues/938)

We would really like to see better support for TinyMCE and to restore it to being a first class citizen in ACF.

Not being able to help out with this issue is unfortunate.

It seems that most issues with TinyMCE are the result of conflicts with WordPress itself.

Isolating the ACF WYSIWYG editor in an iframe might be a viable solution?
Inside the iframe there wouldn't be anything of WordPress to have conflicts with.

We obviously want to help out or contribute financially to this end, please let us know if this is an option.

Start by reviewing the linked discussions in issues #906 and #876, plus the JavaScript-source discussion in issue #938, to understand the current TinyMCE integration and its limitations. The issue does not identify implementation files, tests, or an agreed solution; a contribution would first need a defined scope and acceptance criteria for making TinyMCE a first-class editor.