WP_HTML_Processor::has_self_closing_flag(): bool
- Since
- 6.6.0
- Source
wp-includes/html-api/class-wp-html-processor.php:5209
Description
No HTML elements ought to have the self-closing flag and for those, the self-closing flag will be ignored. For void elements this is benign because they "self close" automatically. For non-void HTML elements though problems will appear if someone intends to use a self-closing element in place of that element with an empty body.
For HTML foreign elements and custom elements the self-closing flag determines if they self-close or not.
This function does not determine if a tag is self-closing, but only if the self-closing flag is present in the syntax.
Compatibility
- WordPress
- since 6.6.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Return value
bool- Whether the currently matched tag contains the self-closing flag.
Performance profile
How much work a call to WP_HTML_Processor::has_self_closing_flag() 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
- 7–8
- Plugin surface
- None
- Called by
- 3
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, depending on the branch taken. The body compiles to 10.
Nothing here hands control to plugin code.
3 places in core call this, so the cost is paid more often than your own code shows.
What one call costs · 2 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_HTML_Processor::has_self_closing_flag() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
->is_virtual() | 7 | ->is_virtual() |
!->is_virtual() | 8 | ->is_virtual(), ::has_self_closing_flag() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 9 | 7 | 1 | 1 fewer instruction than PHP 8.5 |
| 8.5 | 10 | 7–8 | 1 | |
| 8.4 | 10 | 7–8 | 1 | |
| 8.3 | 10 | 7–8 | 1 | |
| 8.2 | 10 | 7–8 | 1 | |
| 8.1 | 10 | 7–8 | 1 | |
| 7.4 | 10 | 7–8 | 1 |
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.
Uses · 2
- WP_HTML_Processor::is_virtual()Indicates if the currently-matched token is virtual, created by a stack operation while processing HTML, rather than a token found in the HTML text itself.
- WP_HTML_Tag_Processor::has_self_closing_flag()Indicates if the currently matched tag contains the self-closing flag.
Used by · 3
- WP_HTML_Processor::expects_closer()Indicates if the currently-matched node expects a closing token, or if it will self-close on the next step.
- WP_HTML_Processor::serialize_token()Serializes the currently-matched token.
- WP_HTML_Processor::step()Steps through the HTML document and stop at the next tag, if any.
Source code
public function has_self_closing_flag(): bool { return $this->is_virtual() ? false : parent::has_self_closing_flag(); }Changelog
Introduced in 6.6.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/html-api/class-wp-html-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.