- From: Ryosuke Niwa <notifications@github.com>
- Date: Thu, 12 Nov 2020 23:09:54 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 13 November 2020 07:10:06 UTC
@rniwa commented on this pull request. > @@ -2667,8 +2672,16 @@ indicated in the <a for=/>remove</a> algorithm below. <li><p><a for=set>Remove</a> <var>node</var> from its <var>parent</var>'s <a for=tree>children</a>. - <li><p>If <var>node</var> is <a for=slottable>assigned</a>, then run <a>assign slottables</a> for - <var>node</var>'s <a>assigned slot</a>. + <li> + <p>If <var>node</var> is <a for=slottable>assigned</a>, then: + + <ol> + <li><p><p>If <var>parent</var>'s <a for=tree>root</a> is a <a for=/>shadow root</a> with its + <a for=tree>root</a>'s <a for=ShadowRoot>slot assignment</a> set to "<code>auto</code>", + then <a for=set>remove</a> <var>node</var> from its <a>assigned slot</a>'s <a>manually assigned nodes</a>. + + <li><p>Run <a>assign slottables</a> for <var>node</var>'s <a>assigned slot</a>. How can this be right? *assign slottables* would set the list of assigned nodes to slottable matching the slot in tree order. It would mean that we're always re-order slottable in the tree order regardless of in what order they're inserted. -- 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/860#discussion_r522710313
Received on Friday, 13 November 2020 07:10:06 UTC