From 7e18bc488c1eec71bb84eeabdf7f2fae320cca8a Mon Sep 17 00:00:00 2001 From: Dominic Farolino Date: Fri, 31 May 2024 13:46:01 +0200 Subject: [PATCH] Fix phrase-level wrapping --- dom.bs | 39 ++++++++++++++++++++------------------- 1 file changed, 20 insertions(+), 19 deletions(-) diff --git a/dom.bs b/dom.bs index 89327bb02..c0dede54f 100644 --- a/dom.bs +++ b/dom.bs @@ -2647,9 +2647,9 @@ of a node into a parent before a child, run the insertion steps for all or some nodes. The algorithm is passed insertedNode, as indicated in the insert algorithm below. These steps must not modify the node tree that insertedNode -participates in, create browsing contexts, fire -events, or otherwise execute JavaScript. These steps may [=queue a global task|queue tasks=] to -do these things asynchronously, however. +participates in, create browsing contexts, +fire events, or otherwise execute JavaScript. These steps may +[=queue a global task|queue tasks=] to do these things asynchronously, however.

While the insertion steps cannot execute JavaScript (among other things), they will @@ -2695,18 +2695,18 @@ do these things asynchronously, however. adjust this further based on the requirements of the script element. There might be other ways to define that though as Olli suggests, so leaving that out for now. --> -

Specifications may also define post-connection steps for all or some nodes. -The algorithm is passed connectedNode, as indicated in the insert -algorithm below. +

Specifications may also define +post-connection steps for all or some +nodes. The algorithm is passed connectedNode, as indicated in the +insert algorithm below. -

The purpose of the post-connection steps is to provide an opportunity for nodes to perform any connection-related operations that modify the node tree that -connectedNode participates in, create browsing contexts, or -otherwise execute JavaScript. These steps allow a batch of nodes to be inserted -atomically with respect to script, with all major side effects occurring after the -batch insertions into the node tree is complete. This ensures that all pending node -tree insertions completely finish before more insertions can occur. +

The purpose of the post-connection steps is to provide an opportunity for +nodes to perform any connection-related operations that modify the node tree +that connectedNode participates in, create browsing contexts, +or otherwise execute JavaScript. These steps allow a batch of nodes to be +inserted atomically with respect to script, with all major side effects +occurring after the batch insertions into the node tree is complete. This ensures +that all pending node tree insertions completely finish before more insertions can occur.

Specifications may define children changed steps for all or some @@ -2813,11 +2813,12 @@ before a child, with an optional suppress observers flag, run

  • Let staticNodeList be a list of nodes, initially « ».

    -

    We collect all nodes before calling the post-connection - steps on any one of them, instead of calling the post-connection steps while - we're traversing the node tree. This is because the post-connection steps can modify - the tree's structure, making live traversal unsafe, possibly leading to the post-connection - steps being called multiple times on the same node.

    +

    We collect all nodes before calling the + post-connection steps on any one of them, instead of calling the + post-connection steps while we're traversing the node tree. This is because + the post-connection steps can modify the tree's structure, making live traversal unsafe, + possibly leading to the post-connection steps being called multiple times on the same + node.