Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how PLAINTEXT elements may contain child nodes. #10540

Merged
merged 8 commits into from
Aug 14, 2024
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -128962,9 +128962,12 @@ document.body.appendChild(text);

<p>Switch the tokenizer to the <span>PLAINTEXT state</span>.</p>

<p class="note">Once a start tag with the tag name "plaintext" has been seen, that will be the
last token ever seen other than character tokens (and the end-of-file token), because there is
no way to switch out of the <span>PLAINTEXT state</span>.</p>
<p class="note">Once a start tag with the tag name "plaintext" has been seen, all remaining
tokens will be character tokens (and a final end-of-file token) because there is no way to
annevk marked this conversation as resolved.
Show resolved Hide resolved
switch the tokenizer out of the <span>PLAINTEXT state</span>. However, as the tree builder
remains in its existing insertion mode, it might <span>reconstruct the active formatting
elements</span> while processing those character tokens. This means that it's possible for a
<code>plaintext</code> element to contain other elements.</p>
annevk marked this conversation as resolved.
Show resolved Hide resolved
</dd>

<!-- button is a hybrid -->
Expand Down