From b096dc024c738c3bfe60ce0ee76d2362aaa23a90 Mon Sep 17 00:00:00 2001
From: Joey Arhar <jarhar@chromium.org>
Date: Mon, 17 Apr 2023 12:29:07 -0700
Subject: [PATCH 1/2] Add before removing steps

The existing "removing steps" allow other specs to run algorithms after a
node has been removed from the tree, but there is no way to run steps
before a node has been removed from the tree.

This patch adds new "before removing steps" to allow other specs to run
algorithms before the node has been removed.

This is needed for this HTML issue:
https://github.com/whatwg/html/issues/9161
---
 dom.bs | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/dom.bs b/dom.bs
index 6eefb816..a692f2c9 100644
--- a/dom.bs
+++ b/dom.bs
@@ -2754,10 +2754,11 @@ within a <var>parent</var>, run these steps:
 </ol>
 
 
-<p><a lt="Other applicable specifications">Specifications</a> may define
-<dfn export id=concept-node-remove-ext>removing steps</dfn> for all or some <a for=/>nodes</a>. The
-algorithm is passed <var ignore>removedNode</var>, and optionally <var ignore>oldParent</var>, as
-indicated in the <a for=/>remove</a> algorithm below.
+<p><a lt="Other applicable specifications">Specifications</a> may define <dfn export
+id=concept-node-remove-ext>removing steps</dfn> and <dfn export
+id-concept-node-before-remove-ext>before removing steps</dfn> for all or some <a for=/>nodes</a>.
+These algorithms are passed <var ignore>removedNode</var>, and optionally <var
+ignore>oldParent</var>, as indicated in the <a for=/>remove</a> algorithm below.
 
 <p>To <dfn export id=concept-node-remove>remove</dfn> a <var>node</var>, with an optional
 <i>suppress observers flag</i>, run these steps:
@@ -2767,6 +2768,12 @@ indicated in the <a for=/>remove</a> algorithm below.
 
  <li><p>Assert: <var>parent</var> is non-null.
 
+ <li><p>Run the <a>before removing steps</a> with <var>node</var> and <var>parent</var>.
+
+ <li><p>For each <a>shadow-including descendant</a> <var>descendant</var> of <var>node</var>, in
+ <a>shadow-including tree order</a>, run the <a>before removing steps</a> with
+ <var>descendant</var>.</p></li>
+
  <li><p>Let <var>index</var> be <var>node</var>'s <a for=tree>index</a>.
 
  <li><p>For each <a>live range</a> whose <a for=range>start node</a> is an

From 35ccfbfadfe8ac11a5705420d43988125a6ae3a6 Mon Sep 17 00:00:00 2001
From: Joey Arhar <jarhar@chromium.org>
Date: Mon, 17 Apr 2023 14:07:28 -0700
Subject: [PATCH 2/2] fix id attribute

---
 dom.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dom.bs b/dom.bs
index a692f2c9..ac85d896 100644
--- a/dom.bs
+++ b/dom.bs
@@ -2756,7 +2756,7 @@ within a <var>parent</var>, run these steps:
 
 <p><a lt="Other applicable specifications">Specifications</a> may define <dfn export
 id=concept-node-remove-ext>removing steps</dfn> and <dfn export
-id-concept-node-before-remove-ext>before removing steps</dfn> for all or some <a for=/>nodes</a>.
+id=concept-node-before-remove-ext>before removing steps</dfn> for all or some <a for=/>nodes</a>.
 These algorithms are passed <var ignore>removedNode</var>, and optionally <var
 ignore>oldParent</var>, as indicated in the <a for=/>remove</a> algorithm below.