Text cursor jumps to ACF WYSIWYG field upon hitting enter key

[TomHWP]

Describe the bug
When editing a page with Gutenberg that contains ACF blocks with a WYSIWYG field the cursor jumps to the last WYSIWYG field on the page.

To Reproduce
Steps to reproduce the behavior:

1. Edit or create a page
2. Add an ACF Block that contains a WYSIWYG field with default settings
3. Switch ACF Block to Edit view
4. Now click the title or a Gutenberg paragraph and hit the Enter key
5. Cursor jumps to the last ACF WYSIWYG field on the page (that is in Edit mode)

Expected behavior
The text cursor should just create a new paragraph instead of jumping to the ACF WYSIWYG field.

Screenshots or Video
https://github.com/user-attachments/assets/6e8ff233-3d42-4d74-835d-b702d169165d

Version Information:

• WordPress Version: 6.7.1
• PHP Version: 7.4
• ACF Version: ACF PRO 6.3.12
• Browser: Chrome

Additional context
I already did some digging. I think it has something to do with TinyMCE because when I enable Delay Initialization (TinyMCE will not be initialized until field is clicked) the cursor doesn't jump to the WYSIWYG field.

[enoversum]

I'm having the exact same issue, and I'm just wondering what causes the issue. I experienced this on another site as well, so it's not any other plugin or theme that interferes here. Thanks for the tip for delayed initialisation, that might help.

[ekazda]

I'm having a similar problem and submitted a ticket directly to ACF. They had this to say:

We’ve passed this information to our development team for further investigation. While we don’t have an ETA for a fix at the moment, we will be looking into the issue. In the meantime, if you come across any additional details that might help narrow it down, feel free to share them.

Also posted in their forums. Hopefully this will be resolved soon.

[enoversum]

I'm having a similar problem and submitted a ticket directly to ACF. They had this to say:

We’ve passed this information to our development team for further investigation. While we don’t have an ETA for a fix at the moment, we will be looking into the issue. In the meantime, if you come across any additional details that might help narrow it down, feel free to share them.

Also posted in their forums. Hopefully this will be resolved soon.

Indeed, thanks for the info. I had just replied to your forum post, so let's hope they will honour it as a bug. It's actually quite a bit older already, I've come across it at least last year at some point, could be something like September or October. I had just forgotten, until it happened again today.

[TomHWP]

Thanks @enoversum & @ekazda for the updates! Hopefully they will fix this asap.

[eyetractive]

We're also running into this issue, impacting some of our clients.