Changeset 55619 for trunk/src/wp-includes/html-api/class-wp-html-tag-processor.php

Timestamp:

04/04/2023 10:04:45 AM (18 months ago)

Author:

Bernhard Reiter

Message:

HTML API: Add has_self_closing_flag() to Tag Processor.

In this patch we're adding has_self_closing_flag() to the HTML Tag Processor.
This exposes whether a currently-matched tag contains the self-closing flag /.

This information is critical for the evolution of the HTML API in order
to track and parse HTML structure, specifically, knowing whether an
HTML foreign element is self-closing or not.

Props dmsnell, zieladam.
Fixes #58009.

File:

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

trunk/src/wp-includes/html-api/class-wp-html-tag-processor.php

@@ -1758 +1758 @@
 
         return strtoupper( $tag_name );
+    }
+
+    /**
+     * Indicates if the currently matched tag contains the self-closing flag.
+     *
+     * 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.
+     *
+     * @since 6.3.0
+     *
+     * @return bool Whether the currently matched tag contains the self-closing flag.
+     */
+    public function has_self_closing_flag() {
+        if ( ! $this->tag_name_starts_at ) {
+            return false;
+        }
+
+        return '/' === $this->html[ $this->tag_ends_at - 1 ];
     }