- From: Noam Rosenthal <notifications@github.com>
- Date: Wed, 10 Apr 2024 05:46:18 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 April 2024 12:46:22 UTC
@noamr commented on this pull request. > @@ -2752,6 +2812,16 @@ before a <var>child</var>, with an optional <i>suppress observers flag</i>, run <var>parent</var> with <var>nodes</var>, « », <var>previousSibling</var>, and <var>child</var>. <li><p>Run the <a>children changed steps</a> for <var>parent</var>. + + <li> + <p>For each <var>node</var> in <var>nodes</var>, in <a>tree order</a>: + + <ol> + <li><p>For each <a>shadow-including inclusive descendant</a> <var>inclusiveDescendant</var> of + <var>node</var>, in <a>shadow-including tree order</a>, run the <a>post-insertion steps</a> with + <var>inclusiveDescendant</var>. + </ol> + </li> Given that we don't often add new post-insertion steps/script runners, and the fact that there aren't that many of those today, is there an observable difference between that and post-insertion steps? To me it doesn't seem material whether we spec it this way or that way, it's a way to express that iframes & scripts never run scriptable side-effects in the middle of the DOM update. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1261#discussion_r1559370128 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1261/review/1991588270@github.com>
Received on Wednesday, 10 April 2024 12:46:22 UTC