HTML API: Abort on text nodes requiring reconstruction#6203
HTML API: Abort on text nodes requiring reconstruction#6203dmsnell wants to merge 2 commits intoWordPress:trunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
Closing this because I don't think that the approach is sound. Favoring the more comprehensive approach of tracking every token in the HTML Processor, in #6054 |
Trac ticket: Core-60455
Alternative to #6054
When reaching text nodes that require creating elements during active format reconstruction, aborts the HTML Processor.
This prevents progressing into a document where the text nodes would change the structure and affect breadcrumbs. Until the HTML Processor properly supports text nodes this makes it possible to continue operating safely.