🐛 To remove el use remove() instead of removeChild() from parent,… #50
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.
… fixing issues where parent gets removed earlier
This is in relation to Issue: #49
For my project this is fixing the issues, I do not really know why this library uses the parent to remove the element already in the variable "el". If there is no specific reason I think remove() is a safer implementation, solving issues where the parent is not accessible.