The new Block Editor field is great, but its current isolated implementation prevents custom RichText formats (registered via wp.richText.registerFormatType) from appearing in inline toolbars (e.g., Paragraph blocks).
These formats work correctly in the main Post Editor and Site Editor, but not inside the Block Editor field—even when scripts are properly enqueued via enqueue_block_editor_assets.
From reviewing the implementation, the field initializes the editor via wp.attachEditor() with Automattic’s isolated-block-editor, which:
• only exposes core formats from wp-format-library
• does not merge or allow custom registered formats
• does not expose allowedFormats or similar configuration
This makes it impossible to use common semantic inline markup such as <abbr>, <dfn>, <cite>, <q>, or controlled <span> formats inside the field (I created a plugin to add these).
Request:
Please consider adding an opt-in way to allow custom RichText formats in the Block Editor field, for example, by:
• exposing a formats/allowedFormats option in the editor settings, or
• merging registered format types during initialization, or
• providing a small JS hook/filter to extend formats.
This would improve accessibility, editorial consistency, and plugin compatibility without changing default behavior for existing users.
.
