By the end of this session, attendees will:<\/p>\n\n\n\n
-> Understand when and why to use the WordPress HTML API instead of traditional methods like regex, str_replace(), or DOMDocument, including specific security vulnerabilities, HTML5 incompatibility issues, and performance problems each legacy approach creates.<\/p>\n\n\n\n
\u2028-> Master WP_HTML_Tag_Processor fundamentals for memory-efficient, single-pass HTML parsing: core methods (next_tag, get\/set_attribute, add\/remove_class), the bookmark system for complex document traversal, and when streaming parsing is sufficient for your needs.\u2028<\/p>\n\n\n\n
-> Utilize WP_HTML_Processor for structure-aware operations: navigate HTML hierarchically using breadcrumbs, track nesting depth, properly match CSS classes, and handle malformed HTML gracefully with built-in error detection.\u2028<\/p>\n\n\n\n
-> Apply real-world use cases beyond block customization: safely sanitize user-generated content, add performance attributes (lazy loading, fetchpriority, decoding) to any HTML source, modify link attributes programmatically, process shortcode or widget output, and enhance accessibility with ARIA attributes.\u2028<\/p>\n\n\n\n
-> Navigate the API’s evolution across WordPress 6.2 through 6.7: understand capability improvements (complete token scanning, text content modification, spec-compliant decoding), recognize current limitations (BODY context, bookmark limits), and prepare for future features (CSS selectors, structural modifications).\u2028<\/p>\n\n\n\n
-> Implement production-ready patterns: integrate the HTML API with WordPress hooks (the_content, render_block, widget_text), write proper error handling for unsupported HTML, choose between Tag Processor’s speed versus HTML Processor’s structure awareness, and migrate existing regex-based code safely.<\/p>\n\n\n\n