Skip to content

Fix ordering of lifecycle callbacks to match implementations #12017

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

Open
lukewarlow wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix ordering of lifecycle callbacks to match implementations #12017

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
19 changes: 9 additions & 10 deletions source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76830,13 +76830,12 @@ document.body.append(parent);
<dt>A collection of <dfn
data-x="concept-custom-element-definition-lifecycle-callbacks">lifecycle callbacks</dfn></dt>
<dd>A map, whose keys are the strings "<code data-x="">connectedCallback</code>", "<code
data-x="">disconnectedCallback</code>", "<code data-x="">adoptedCallback</code>", "<code
data-x="">connectedMoveCallback</code>", "<code data-x="">attributeChangedCallback</code>",
"<code data-x="">formAssociatedCallback</code>", "<code data-x="">formDisabledCallback</code>",
"<code data-x="">formResetCallback</code>", and "<code
data-x="">formStateRestoreCallback</code>". The corresponding values are either a Web IDL <code
data-x="idl-Function">Function</code> callback function type value, or null. By default the value
of each entry is null.</dd>
data-x="">disconnectedCallback</code>", "<code data-x="">connectedMoveCallback</code>", "<code
data-x="">adoptedCallback</code>", "<code data-x="">attributeChangedCallback</code>", "<code
data-x="">formAssociatedCallback</code>", "<code data-x="">formDisabledCallback</code>", "<code
data-x="">formResetCallback</code>", and "<code data-x="">formStateRestoreCallback</code>". The
corresponding values are either a Web IDL <code data-x="idl-Function">Function</code> callback
function type value, or null. By default the value of each entry is null.</dd>

<dt>A <dfn data-x="concept-custom-element-definition-construction-stack">construction
stack</dfn></dt>
Expand Down Expand Up @@ -77116,9 +77115,9 @@ dictionary <dfn dictionary>ElementDefinitionOptions</dfn> {

<li><p>Let <var>lifecycleCallbacks</var> be the <span>ordered map</span> «[ "<code
data-x="">connectedCallback</code>" → null, "<code data-x="">disconnectedCallback</code>" →
null, "<code data-x="">adoptedCallback</code>" → null, "<code
data-x="">connectedMoveCallback</code>" → null, "<code
data-x="">attributeChangedCallback</code>" → null ]».</p>
null, "<code data-x="">connectedMoveCallback</code>" → null, "<code
data-x="">adoptedCallback</code>" → null, "<code data-x="">attributeChangedCallback</code>"
→ null ]».</p>

<li>
<p>For each <var>callbackName</var> of <span data-x="map get the keys">the keys</span> of
Expand Down