Bugfix #173 - Guard against possible falsy node.children values #174
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your contribution! |
|
@reppners Thank you for merging this in! Just curious, when do you think this could be released? |
|
@johanquiroga Published now as 3.0.0-rc.0 :) Ride safe! 🏍️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The purpose of this PR is to add a check against undefined values when checking for node children within the
removePointerEventsFromShadoDomChildNodesfunction.Unfortunately, I don't have a way of reproducing this yet, but I tracked down the error mentioned in #173 to this. Using this patch fixes the issue for me.
This should fix #173.