HTML API: Plans for 6.7

[dmsnell]

🔝Block API | HTML issues | Refactors | ↑ Broader Roadmap | ← Plans for 6.6 | → Plans for 6.8

Lingering work from 6.6

• [x] Review all of the push/pop mechanics and polish them, figure out the proper comprehensive model of operation, and refactor the internals to ensure they are elegant and can be introspected.

Added Spec Support (Core-61576)

• Tag supports:

  • [ ] SVG and MathML foreign content.
    • WordPress/wordpress-develop#6006
  • [ ] TABLE support.
    • WordPress/wordpress-develop#6040
  • [x] SELECT support.
    • WordPress/wordpress-develop#5908
  • [ ] FORM support.
  • [ ] TEMPLATE support.
  • [ ] PLAINTEXT support.
    • WordPress/wordpress-develop#5905

• Various supports:

  • WordPress/wordpress-develop#6973
  • Wordpress/wordpress-develop#6983
  • WordPress/wordpress-develop#6982
  • WordPress/wordpress-develop#6020
  • WordPress/wordpress-develop#6972
  • WordPress/wordpress-develop#6977
  • WordPress/wordpress-develop#6981

• [ ] Parse DOCTYPE public and system identifiers, used for detecting quirks mode.

• Testing and verification (Core-61646, Core-61530)

  • WordPress/wordpress-develop#6984
  • WordPress/wordpress-develop#6985

New Features and Interfaces

• [ ] Core-61617 Add set_modifiable_text() for plaintext-only modifications.
  • WordPress/wordpress-develop#7007

Bug Fixes

• Core-61560 The Fragment parser should not add the context node to the stack of open elements.
• Core-61851 HTML_Processor::next_tag() should respect the tag_name argument.
  • WordPress/wordpress-develop#6980
• Various fixes:
  • WordPress/wordpress-develop#6988

Enhancements

• Core-61545 General performance improvements.

  • WordPress/wordpress-develop#6890

• [ ] Audit and revamp of CSS class behaviors to conform more closely to the spec. I.e. quirks mode vs. no-quirks mode.

Blocks

• [ ] Continue developing block attribute sourcing.
• [ ] Iterate on the Server Directive Processor.
• [ ] Iterate on the Block Bindings processor.

Not likely in 6.7

• [ ] Setting inner or outer HTML because it should parse the provided new HTML in a fragment parser whose context node is the one in which it is found. Also, because we have to solve the problem of composition and avoiding re-parsing every level of inner content.
  • With outside help a form of this may make it in to 6.7.

Backports into Gutenberg

• WordPress/gutenberg#63089