Re: [whatwg/dom] Add Imperative Slot API (#966)

@annevk commented on this pull request.



>  
  <li>
-  <p>For each <a>slottable</a> <a for=tree>child</a> of <var>host</var>, <var>slottable</var>, in
+  <p>Otherwise, for each <a>slottable</a> <a for=tree>child</a> of <var>host</var>, <var>slottable</var>, in

Oh no, it got confusing. That's not what Mason or I mean. That particular comment was based on a misunderstanding.

`assign()` always succeeds (and doesn't no-op or throw), as per the current HTML PR. And moving a slot around doesn't affect its manually assigned nodes, as per this PR.

And the answer to your question in this subthread OP is that manually assigned nodes would be ignored in that case as it would be quite esoteric if moving a `slot` element around is a no-op for manually assigned nodes except if you move it to a shadow tree with named slot assignment.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/966#discussion_r612966587