Fix errors caused by mutations on certain elements #2
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.
In my use case, we are having to modify the
d
attribute on apath
element inside of ansvg
tag. This is triggering the MutationObserver. However, theNode
object returned by thepath
element in javascript is not compatible with the expectations in this observer. It still has aclassName
property, but it is not a string type but aSVGAnimatedString
. ThisSVGAnimatedString
type does not have anincludes
property causing these calls to error out.While it may not be the most elegant fix, adding in a check to see if the includes property is defined fixes this error in my specific use case.