🔝Block API | HTML issues | Refactors | ↑ Broader Roadmap | ← Plans for 6.5 | → Plans for 6.7

Plans for the HTML API in WordPress 6.6 are being reassessed.
Most likely there will be two goals for the release:

• Complete and rely on a custom and spec-compliant encoder/decoder.
  • Core-60841 WP_Token_Set class for named character reference lookup.
    Token Map: Introduce an efficient lookup and translation class for string mappings. wordpress-develop#5373
  • Core-61072 Spec-compliant text decoder.
    HTML API: Add custom text decoder wordpress-develop#6387
• Design how to communicate when an HTML document has retroactively changed, allow calling code to match on, stop at, and modify implicitly-created elements, including when elements are closed.
  • HTML API: Return elements pushed and popped rather than tags read. wordpress-develop#6348

Fixes

• HTML API: Fix tag processor token length wordpress-develop#6625

Ideas

• Can we detect transitions from HTML and SVG/MathML namespaces in the Tag Processor?
  • Probably not, because once entering HTML contexts we have to obey HTML rules to know when to exit that content, before returning to XML-like parsing.