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.

Sign up for GitHub

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

Jump to bottom

Editorial: fix typo in custom elements section #10620

Merged
merged 1 commit into from
Sep 16, 2024
Merged

Editorial: fix typo in custom elements section #10620

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72892,7 +72892,7 @@ customElements.define("x-foo", class extends HTMLElement {
data-x="custom-element-upgrades">upgrades</span> as well.)</p>

<p>Each <span>custom element reactions stack</span> has an associated <dfn>backup element
queue</dfn>, which an initially-empty <span>element queue</span>. Elements are pushed onto the
queue</dfn>, which is an initially-empty <span>element queue</span>. Elements are pushed onto the
<span>backup element queue</span> during operations that affect the DOM without going through an
API decorated with <code data-x="CEReactions">[CEReactions]</code>, or through the parser's
<span>create an element for the token</span> algorithm. An example of this is a user-initiated
Expand Down