If when a page loads a user starts on the text tab of a WYSIWYG (either the post content or a meta box) and clicks the visual tab - although the UI looks to have changed - the content still reads from the text tab.
This means clicking the text tab does nothing as it thinks it is on that tab already.
Entering any content in the visual tab does not save - as the saved value is taken from the text tab.
Clicking the visual tab a second time loads the tab properly.
This is a classic editor post (regards less of if the post type supports the body), Metabox 5.4, WordPress 5.7 and a clean install with no other plugins.
Not the normal post content WYSIWYG work fine on classic editor, but if you add a meta box WYSIWYG to the post type the normal one then breaks.
I am guessing you have a hook that requires some JS that is only in the Gutenberg view. There are no console errors.
Thank you for your feedback.
I've informed the development team to check this case. I will get back to you if there is any information.
Has there been any progress on this? This is still a live issue.
This is still a issue with the latest metabox on the latest wordpress that wysiwyg does not load to the visual tab correctly.
I have also problems with the wysiwyg and install today the latest metabox 5.4.6 and WordPress 5.8.
the problem is still present
This is turning in to a major problem for us and our clients.
Metabox code breaks the transition from 'Text' to 'Visual'. This has been the case for months.
Can we please get a reply or an indication that this is being looked at?
We've received a lot of feature requests and reporting issues. The development team is working tirelessly to fix the issue but it will take time to do that. Thanks for your patience.
Any update on this? The WYSIWYG field is still breaks WP
Just bumping to say that this is still a bug. On a clean wordpress site if a user starts on the text view of a WYSIWYG clicking the 'Visual' tab does not actually move one over to visual. One needs to click twice. This causes all sorts of issue like content not being saved, or incorrect preview.
This but was never resolved, still having this issue in 2023