Skip to content

Conversation

foolip
Copy link
Member

@foolip foolip commented Oct 22, 2025

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
    • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
    • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
  • Corresponding HTML AAM & ARIA in HTML issues & PRs:
  • MDN issue is filed: …
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


/indices.html ( diff )
/parsing.html ( diff )
/scripting.html ( diff )

@foolip foolip changed the title Add <template contentmethod declarative out-of-order streaming Add <template contentmethod> for declarative out-of-order streaming Oct 22, 2025
@foolip foolip marked this pull request as draft October 22, 2025 15:05

<li><p>Depending on the contentmethod state, remove existing nodes and update the insertion point.</p></li>

<li><p>Question: do we adjust the insertion point simply by setting <var>adjusted insertion location</var>,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit more involved because we need to adjust the location based on the grandparent's contentmethod and the parent's contentname.

<li><p>TODO: what to we need to do so that elements are inserted into the template element
and redirected by our pre-insertion steps? We need to undo whatever it is that causes nodes
to be inserted into the DocumentFragment normally.</p></li>
</ol>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the "adjusted insertion location" or whatever it's called

</li>

<li>
<!-- TODO: is it OK if both of these branches run? If not, which one wins? -->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not OK. One needs to win.

element with a valid contentmethod attribute, find the target element with the same namespace,
localName, and a contentname attribute with the same value.</p></li>

<li><p>TODO: is there any whitespace stripping in contentname attribute values?</p></li>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should work the same as ID referencing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants