I have just run into an issue when trying to add content to a WYSIWYG field when using a chrome based browser.
I have a CTP that supports the standard Gutenburg post editor and has a single wysiwyg field. When I add or edit a post to that CTP using a chrome based browser I cannot interact with the content area on the 'Visual' tab ('Text' tab is fine).
This issue is still present when I deactivate all plugins (including oxygen builder) on a live (staging) site, and I can reproduce the issue on a clean local dev site running Bricks Builder. See the screenshot at the following dropbox link for more context.
I think this something to do with new versions of chrome - a client of mine was able to use the WYSIWYG field fine in March 2023 and with no changes/updates on the website (except for may be updating to WP 6.2.2) but found it was broken when they tried to use it today.
To tried to trouble shoot the issue, I updated all plugins / themes etc. to the newest versions, then tried disabling everything until only Meta Box & Meta Box AIO were active. I could easily reproduce the issue on a new site on local dev (which is were the screenshot is from).
Let me know if you need any more info.
This issue has been fixed in this commit https://github.com/wpmetabox/meta-box/commit/89d7f8a556954492a3dbcecaf5b6726fecd71445
you can apply the changes on your site, clear browser cache and let me know how it goes.
hi, im not familiar with what it means to apply the changes in the commit in the context of wordpress. do i paste that code somewhere in WP? sorry, im new to this stuff, but my client absolutely needs to be able to interact with the visual editor.
for clarity, im using the metabox AIO plugin and not familiar
Hi Michael, I imagine Peter means that you overwrite the wysiwyg.js file with the contents in the github commit. I haven't tried replacing the wysiwyg.js file with the new code yet as my client was fine with using Firefox (works fine in FF or Safari by the way) and I'll probably wait until the next plugin update release.
Sorry Michael, I just heard back from my client and even though they can use the wysiwyg field in firefox, saving the post doesn't save the wysiwyg field data. So it looks like I will be trying the temp fix suggested above by Peter.