HTML API: Refactors

[dmsnell]

HTML issues | Refactors | ↑ HTML API Roadmap

Planned

• HTML API: Use Tag Processor instead of RegExp for URL details controller wordpress-develop#5547

Reported

• Core-30324

Places the HTML API replaced string/regex logic

• Gallery: register styles with style engine #43070
• Block Library: Refactor core blocks to use HTML Tag Processor #43178 (this eventually morphed into behaviors, which would have been performing regex logic otherwise)
• Try adding layout classnames to inner block wrapper #44600 (following PRs expanded the use of the Tag Processor; some replaced logic, some built new logic)
• Update/block support settings use tag processor #46625
• Replace regex with tag processor for duotone class render #49212
• Search block: refactor to use HTML Tag Processor #51273
• Refactor ImageCDN parsing to rely on HTML API instead of RegExps Automattic/jetpack#32700
• Media & text: Update the image replacement logic #62030
• wp_audio_shortcode() outputs invalid HTML wordpress-develop#6917

Places the HTML API was introduced in new code

• Add a current-menu-ancestor class to navigation items #40778
• [Heading block] Add a wp-block-heading CSS class #42122
• Design Tools: Add a Position block support (including sticky), decoupled from layout #46142
• Experimental: Navigation block with the Interactivity API #50041
• Allow contents of Paragraph to be "connected" to a meta custom field #53247
• Query block: client-side pagination #53812
• Block Supports: Add background image support to Group block #53934

Rework of how the HTML API is being used

• WIP: Only send one class name to HTML API's add_class() #54873

---

Subsystems relying on HTML API:

• block settings
• block library
• navigation
• search