WP_Block_Processor::is_html(): bool
- Since
- 6.9.0
- Source
wp-includes/class-wp-block-processor.php:1613
Compatibility
- WordPress
- since 6.9.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in 3 of the 5 tracked releases, added in 6.9.0, and compiles on PHP 7.4 through 8.6-dev.
Return value
bool- Whether the processor is matched on an HTML span.
Performance profile
How much work a call to WP_Block_Processor::is_html() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.
- Cost class
- Trivial
- Scaling
- Constant
- Instructions
- 4
- Plugin surface
- None
- Called by
- 9
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 4.
Nothing here hands control to plugin code.
9 places in core call this, so the cost is paid more often than your own code shows.
What one call costs · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Block_Processor::is_html() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 4 | none |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 4 instructions, 4 executed per call, 0 branches. The work does not change between versions.
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Used by · 9
- WP_Block_Processor::allocate_and_return_parsed_attributes()Attempts to parse and return the entire JSON attributes from the delimiter, allocating memory and processing the JSON span in the process.
- WP_Block_Processor::extract_full_block_and_advance()Extracts a block object, and all inner content, starting at a matched opening block delimiter, or at a matched top-level HTML span as freeform HTML content.
- WP_Block_Processor::get_block_type()Allocates a substring for the block type and returns the fully-qualified name, including the namespace, if matched on a delimiter, otherwise `null`.
- WP_Block_Processor::get_html_content()Returns the string content of a matched HTML span, or `null` otherwise.
- WP_Block_Processor::get_printable_block_type()Allocates a printable substring for the block type and returns the fully-qualified name, including the namespace, if matched on a delimiter or freeform block, otherwise `null`.
- WP_Block_Processor::is_block_type()Indicates if the block delimiter represents a block of the given type.
- WP_Block_Processor::is_non_whitespace_html()Indicates if the matched delimiter is an HTML span and comprises more than whitespace characters, i.e. contains real content.
- WP_Block_Processor::next_delimiter()Advance to the next block delimiter in a document, indicating if one was found.
- WP_Block_Processor::opens_block()Indicates if the matched delimiter is an opening or void delimiter of the given type, if a type is provided, otherwise if it opens any block or implicit freeform HTML content.
Source code
public function is_html(): bool { return self::HTML_SPAN === $this->state; }Changelog
Introduced in 6.9.0. Unchanged from 6.9.7 through 7.1.0.
Signature, return type and hooks compared across 3 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-block-processor.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it. - Corrections
- Something wrong on this page? Report it and it gets fixed in the next regeneration.