This PR fixes an issue where a series of mutations could throw errors because the previous sibling that was referenced in the MutationRecord from the MutationObserver in the runner would not actually be a sibling of the nodes being added (nor would it be a child of the target / parent).
The fix is to use the current (eventual state) previous sibling of the first addedNode.
What kind of changes does your PR introduce? (check at least one)
[x] Bugfix
Does your PR introduce a breaking change? (check one)
This PR fixes an issue where a series of mutations could throw errors because the previous sibling that was referenced in the
MutationRecordfrom theMutationObserverin the runner would not actually be a sibling of the nodes being added (nor would it be a child of the target / parent).The fix is to use the current (eventual state) previous sibling of the first
addedNode.What kind of changes does your PR introduce? (check at least one)
Does your PR introduce a breaking change? (check one)
Does your PR fulfill the following requirements?