HTML API: Plans for WP 6.6

[dmsnell]

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

---

⚠️ This issue was created from where the discussion originally took place.

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.

[dmsnell]

Thanks @fabiankaegy - this work is independent of and outside of the Gutenberg plugin. It's only here because people wanted to see the plans for the work here. There is nothing in this that relates to Gutenberg or its timelines.

[fabiankaegy]

@dmsnell Sorry for the confusion on my end :)

[dmsnell]

No worries @fabiankaegy. It's all confusing, and in this new home as an issue we can't thread the responses, which is something I miss. Now it's here forever, but that's okay. 😄

[gziolo]

Work on WP 6.6 successfully wrapped up, and we now have a similar issue for WP 6.7 at #60396.