I was able to recreate this in a fresh install of WordPress using TwentyTwentyFive theme and modifying the code enough to create two custom ACF Gutenberg Blocks using acf_register_block.
In one of these blocks I apply a WYSIWYG field that is initiated on page load (initiation is not deferred to onclick). The other block contains a single text field.
I then begin adding these blocks to my page. WYSIWYG block first, about a half dozen text blocks, and then I end with another WYSIWYG block. If I then go back up-page and insert a block of ANY type, as soon as I insert the block my cursor focus is hijacked and placed in the last instance of a WYSIWYG field.
This is occurring on at least two of my production sites that are both using ACF Pro 6.3.12. And again I was able to replicate this with a fresh install of WordPress also using ACF Pro 6.3.12.
Is anyone else experiencing this issue?
I use the WYSIWYG field inside a repeater for an ACF block, so naturally, I also have multiple instances of the WYSIWYG field on a page. I suffer from the same issue. As soon as I hit Enter anywhere in Gutenberg, my cursor jumps to the last WYSIWYG field in my ACF block. There is also a GitHub issue describing the same issue.
We also have this problem recently and the cursor always jumps to the last WYSIWYG field in our custom ACF blocks. This is particularly annoying for pages with a lot of content
It seems to occur when starting the insert block process above an existing ACF block that contains a WYSIWYG in Visual mode, focus is dropped down to the next TINYMCE instance. Starting the insert block process below all ACF WYSIWYGs (or if the WYSIWYGs are in Text mode) does not shift focus.
@benplum I believe I also experienced this when the next blocks are below the ACF blocks with a WYSIWYG field. I was on a video call adding stuff at the bottom of a page, when the cursor jumped to my accordion ten feet above the current position 🙂 .
Dear all,
I get the same issue, i agree that it is particularly annoying for pages with a lot of content
# solution :
On each WYSIWYG field, in the “Presentation tab”
check the option : “Delay Initialization, TinyMCE”
I am also having this problem. It’s very annoying.
