Expose TinyMCE editor content manipulation APIs in Gutenberg

[pavelthq]

Please make sure that there is same api for setContent, getContent and getting the editor wrapper as in current version of tinymce.

Many compatibility issues can be solved if there will be same api for settings the content.

wp.tinymce.get('content').setContent('something').

[jaswrks]

Related: https://wordpress.org/support/topic/breaking-compatibility-api/

[danielbachhuber]

Hi @AngeIII,

Thanks for the report. Can you document what does and doesn't currently work?

[pavelthq]

@danielbachhuber Hello, I already wrote in ticket start:

• wp.tinymce.get('content') - getting the "Editor" instance
• wp.tinymce.get('content').setContent('customContent')

also, there was some twinks and abilities to show source/html mode API.

[danielbachhuber]

Related #6648

[gziolo]

@iseulde, what's your opinion on this one? I don't think we want to expose internal TinyMCE API for every RichText component. What would be the alternative?

[adamsilverstein]

I don't think we want to expose internal TinyMCE API for every RichText component.

Maybe not every API? Why not expose common TinyMCE API points like getContent and setContent which could be extremely useful/required for certain extension use cases?