Changeset 56380 for trunk/src/wp-includes/html-api/class-wp-html-processor-state.php

Timestamp:

08/10/2023 08:35:55 AM (17 months ago)

Author:

Bernhard Reiter

Message:

HTML API: Add support for BUTTON element.

This patch adds support to process the BUTTON element. This requires adding some additional semantic rules to handle situations where a BUTTON element is already in scope.

Also included is a fixup to enforce that WP_HTML_Processor::next_tag() never returns for a tag closer. This is useful with the Tag Processor, but not for the HTML Processor. There were tests relying on this behavior to assert that internal processes were working as they should, but those tests have been updated to use the semi-private step() function, which does stop on tag closers.

This patch is one in a series of changes to expand support within the HTML API, moving gradually to allow for more focused changes that are easier to review and test. The HTML Processor is a work in progress with a certain set of features slated to be ready and tested by 6.4.0, but it will only contain partial support of the HTML5 specification even after that. Whenever it cannot positively recognize and process its input it bails, and certain function stubs and logical stubs exist to structure future expansions of support.

Props dmsnell.
Fixes #58961.

File:

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

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

@@ -109 +109 @@
 
     /**
+     * The frameset-ok flag indicates if a `FRAMESET` element is allowed in the current state.
+     *
+     * > The frameset-ok flag is set to "ok" when the parser is created. It is set to "not ok" after certain tokens are seen.
+     *
+     * @since 6.4.0
+     *
+     * @see https://html.spec.whatwg.org/#frameset-ok-flag
+     *
+     * @var bool
+     */
+    public $frameset_ok = true;
+
+    /**
      * Constructor - creates a new and empty state value.
      *