HTML API: Backport updates from Core

[dmsnell]

Updates from WordPress/wordpress-develop from 54a09a7 to 7a71339

• Coding style changes.

• HTML API: Add explicit handling or failure for all tags wordpress-develop#5762 Adds support for the "any other tag" sections in the HTML Processor.

• HTML API: Add support for list elements. wordpress-develop#5539 Adds support for list elements in the HTML Processor.

• HTML API: Add HR tag handling wordpress-develop#5897 Adds support for HR elements in the HTML Processor.

• HTML API: Handle area, br, embed, keygen, wbr wordpress-develop#5895 Adds support for the AREA, BR, EMBED, KEYGEN, and WBR elements in the HTML Processor.

• HTML API: Add PRE and LISTING tag handling wordpress-develop#5903 Adds support for the PRE and LISTING elements in the HTML Processor.

• HTML API: Cleanup tests and list of void elements. wordpress-develop#5913 Updates "all other tags" support in HTML Processor and updates list of void elements.

• HTML API: Handle param, source, track tags wordpress-develop#5906 Adds support for the PARAM, SOURCE, and TRACK elements in the HTML Processor.

• HTML API: Handle input tags wordpress-develop#5907 Adds support for the INPUT element in the HTML Processor

• HTML API: Provide mechanism to scan all tokens in an HTML document, not only the tags. wordpress-develop#5683 Provides mechanism to scan all tokens in an HTML document in the Tag Processor.

• HTML API: Fix splitting single text node wordpress-develop#5976 Avoids splitting text nodes on "<" character.

• HTML API: Fix CDATA lookalike matching invalid CDATA wordpress-develop#5992 Only recognize true CDATA-lookalike nodes.

• HTML API: Fix void tag nesting with next_token wordpress-develop#5975 Prevent void tag nesting when calling next_token()

• HTML API: Reset parser state after seeking to bookmark. wordpress-develop#6021 Reset parser state after seeking.

• https://core.trac.wordpress.org/changeset/57528 Fix typo in setting token flag.

• HTML API: Join text nodes on invalid-tag-name boundaries. wordpress-develop#6041 Ensure consecutive text is all joined into one text node.

The PHP files in the compatability layer are merged and maintained in the Core repo and all changes or updates need to happen first in Core and then be brought over to Gutenberg as built files.

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/compat/wordpress-6.5/html-api/class-gutenberg-html-processor-6-5.php
❔ lib/compat/wordpress-6.5/html-api/class-gutenberg-html-tag-processor-6-5.php

[github-actions]

Flaky tests detected in 577d4e9.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7690811472
📝 Reported issues:

• [Flaky Test] directives inside islands should not be hydrated twice #58332 in /test/e2e/specs/interactivity/tovdom-islands.spec.ts

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core SVN

Core Committers: Use this line as a base for the props when committing in SVN:

Props dmsnell, gziolo.

GitHub Merge commits

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dmsnell <dmsnell@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[gziolo]

I trust you 😀

[dmsnell]

I trust you 😀

bold move 😉

thankfully these are only backports, so they represented reviewed, accepted, and merged code. thank you @gziolo