Fixes distribution of item template via named slots (Fixes 479) #480
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.
This PR fixes #479 by having each stamped instance of an item template inherit the slot attribute on the template item. In the
_createPool
function, the template is stamped and each new instance is appended as children to the template's parent node. When the template reaches theiron-list
element via named slots, this will result in an incorrect distribution of the new nodes, becauseiron-list
will not be able to correctly identify its assigned nodes.See #479 for reasoning behind this approach over modifying the behavior of
Polymer.Templatizer
and a work around until this lands.The accompanying tests use two levels of
slot
ing to demonstrate this.