Undo (keyboard shortcode) not working in meta box area

[rilwis]

Description

This issue might be related to #18755. But the scope of #18755 is wide and covers other things. So I open this issue to be more specific.

When adding any text/textarea custom field to posts using a plugin like Meta Box, ACF (or any method that register meta box with add_meta_box function); or use a plugin that register a normal meta box like Slim SEO, we can't undo the changes inside input boxes provided by these plugins. Pressing Cmd/Ctrl + Z does nothing.

Step-by-step reproduction instructions

1. Install the Slim SEO plugin, it register a meta box under the post content
2. Edit a post
3. Enter some text in the meta title or meta desription
4. Press Cmd/Ctrl + Z and see it does nothing

Screenshots, screen recording, code snippet

No response

Environment info

WordPress 5.9. Use default standard, not the Gutenberg plugin individually.

Tried with Slim SEO 3.13.1 and Meta Box 5.5.1.

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[maksymmamontov]

Can confirm that Undo is inconsistent not only Advanced Custom Fields but in all the input/textarea fields in native Gutenberg Editor.

[hj-collab]

@Thelmachido Did you even read the issue? OP is talking about undo inside the meta box area and not in the post content area. Try undoing inside Meta title, Meta description fields.

[Thelmachido]

@hj-collab thanks for the ping, I followed the reproduction steps and I missed a few things there. My apologies for the mixup, I will check the steps again.

[ndiego]

This issue was reviewed in today's Editor Bug Scrub and has been confirmed.

[maksymmamontov]

@ndiego anyway I can help with fixing this issue?

[maksymmamontov]

@ndiego could you please just add two exceptions for Undo key, so it won't trigger default Gutenberg Undo functionality for textarea and input.
this minor fix will solve 99% of this issue.

[landwire]

@ndiego
This is a very old threat, but the issue is still not resolved. Was there any outcome of the bug scrub and will this problem be fixed at some point?

[ndiego]

will this problem be fixed at some point?

I cannot say for sure, and anyone is welcome to submit a PR, but metaboxes cause a number of other issues in the Editor, and there is a concerted effort to encourage developers to use alternative options. I know I have for all my projects. Here are a few relevant links:

• Move legacy meta boxes to toggle #59242
• Create "How to" guide in block editor handbook for moving away from legacy metaboxes #59804

@ryanwelcher and I actually ran a Developer Hours session on this topic back in May. You can find the recording on WordPress.tv.

[landwire]

@ndiego
Thank you for the update, clarification and relevant links.
I have not checked out the recording yet, so maybe alternative options are viable.
I am using ACF Pro at the moment to create the fields for custom blocks, as it is a very fast workflow without having to have additional build steps or React knowledge.
Is there any info in the recording on how to replace that ACF Pro workflow without deep React knowledge?