fix: ensure child node is a child of parent before removing #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes glimmerjsGH-1401
If
current
isn't a child ofparent
callingparent.removeChild(current)
will result in the error:Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node
. This commonly occurs when the DOM is externally modified by a browser, such as when translating a page. ThenextSibling
may not be a child node ofparent
.current.parentNode?.removeChild(current)
ensures we are only removing a child node of a parent node.