Changeset 61509 for trunk/src/wp-includes/class-wp-block-processor.php

Timestamp:

01/22/2026 01:11:50 AM (4 months ago)

Author:

dmsnell

Message:

Blocks: Ensure extract_full_block_and_advance() matches parse_blocks()

The behavior of WP_Block_Processor::extract_full_block_and_advance() should produce an identical output to what parse_blocks() would return on the same substring of input.

Unfortunately, when HTML spans followed inner blocks, they were being omitted in the output parse tree. This was due to an omission in the original code which would look for those blocks before advancing again after calling extract_full_block_and_advance() recursively.

This patch adds the missing check and resolves the discrepancy.

Developed in: ​https://github.com/WordPress/wordpress-develop/pull/10769
Discussed in: https://core.trac.wordpress.org/ticket/64538

Follow-up to [60939].

Props dmsnell, jonsurrell, jorbin.
Fixes #64537.

File:

• trunk/src/wp-includes/class-wp-block-processor.php (modified) (1 diff)

trunk/src/wp-includes/class-wp-block-processor.php

@@ -1296 +1296 @@
                 $block['innerContent'][] = null;
             }
+
+            /*
+             * Because the parser has advanced past the closing block token, it
+             * may be matched on an HTML span. This needs to be processed before
+             * moving on to the next token at the start of the next loop iteration.
+             */
+            if ( $this->is_html() ) {
+                $chunk                   = $this->get_html_content();
+                $block['innerHTML']     .= $chunk;
+                $block['innerContent'][] = $chunk;
+            }
         }