CFS (Custom Field Suite) WYSIWYG field displays differently in Gutenberg vs. Classic Editor.
The WYSIWYG field will render with equivalent functionality in Classic Editor and Gutenberg.
The WYSIWYG field renders with TinyMCE buttons in Classic Editor and without TinyMCE buttons in Gutenberg.
_Gutenberg 1.6.0
Windows 10
Chrome 61.0.3163.100 (Official Build) (64-bit)_


Hi @chthonic-ds,
Thank you for the report. Most likely TinyMCE is not being enqueued properly or something of that nature. I will look into it. Is CFS on the WordPress.org Plugins Repository?
Thanks @BE-Webdesign. The repository link is noted in the issue: https://wordpress.org/plugins/custom-field-suite/.
This is not the issue with this plugin only. Any plugin that uses wp_editor() to embed TinyMCE editor in metaboxes is broken, sometimes completely, in some cases, only TinyMCE Visual tab is broken and Text tab shows toolbar, but no content area.
This is the same for ACF WYSIWYG fields. It also prevents the Add media, insert images, and add forms from working in using Gravity Forms, and Unsplash Image plugin.
Unfortunately because of this issue. This plugin is unusable for me.
Yep Pods is broken too. See below for an example, I had to click into Text tab since Visual tab is empty to type that text shown.

Yep, it's for any metabox with a wp_editor() function call as said by @dev4press.
Too time consuming for me to look into the code, I don't know the tinymce part of WP, either Gutenberg at all, but it's a major issue, no doubt about that.
I will do my best to resolve this somehow, hopefully before the end of the month.
Most helpful comment
I will do my best to resolve this somehow, hopefully before the end of the month.