Queuing of mutation records looks inconsistent

[nox]

To replace a child with node within a parent, the mutation record is queued after the removal of child and insertion of node:

11. Remove child from its parent with the suppress observers flag set.
12. Let nodes be node’s children if node is a DocumentFragment node, and a list containing solely node otherwise.
13. Insert node into parent before reference child with the suppress observers flag set.
14. Queue a mutation record of "childList" for target parent with addedNodes nodes, removedNodes a list solely containing child, nextSibling reference child, and previousSibling previousSibling.

That behaviour is the same to replace all a node within a parent:

4. Remove all parent’s children, in tree order, with the suppress observers flag set.
5. If node is not null, insert node into parent before null with the suppress observers flag set.
6. Queue a mutation record of "childList" for parent with addedNodes addedNodes and removedNodes removedNodes.

But for example, to insert a node into a parent before a child, mutation records are queued before the actual mutations:

4. If node is a DocumentFragment node, queue a mutation record of "childList" for node with removedNodes nodes.
5. If node is a DocumentFragment node, remove its children with the suppress observers flag set.

Shouldn't all mutation records be queued after the tree was mutated? I understand that because micro tasks are used it doesn't matter much, but the ordering inconsistency makes it look like it actually matters.

[annevk]

You were going to PR this, correct?

[annevk]

Thank you for your PR. I ended up removing a redundant newline before committing and did not want to bother you with that. Hence the distinct commit.