Fix nextSibling after appendChild #3585
Closed
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
If ref_node is undefined instead of null, node.__dom.nextSibling is undefined too. Because of this, Polymer.dom(node).nextSibling is the nextSibling in the browser DOM instead of null.
|
Fixes #3730. |
sorvell
pushed a commit
that referenced
this pull request
Jun 22, 2016
|
Closed in favor of #3731. |
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.
If
ref_nodeis undefined instead ofnull, node.__dom.nextSibling isundefinedinstead ofnulltoo. Because of this, Polymer.dom(node).nextSibling is thenextSibling in the browser DOM when it should be
null.