You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for what it's worth, my temp fix is to always check in _updateChildNodes/shady.html if the real parentNode is the container. See code below.
_updateChildNodes: function(container,children){varcomposed=getComposedChildren(container);varsplices=Polymer.ArraySplice.calculateSplices(children,composed);// process removalsfor(vari=0,d=0,s;(i<splices.length)&&(s=splices[i]);i++){for(varj=0,n;(j<s.removed.length)&&(n=s.removed[j]);j++){if(container===n.parentNode){remove(n);}composed.splice(s.index+d,1);}d-=s.addedCount;}// process addsfor(vari=0,s,next;(i<splices.length)&&(s=splices[i]);i++){next=composed[s.index];for(varj=s.index,n;j<s.index+s.addedCount;j++){n=children[j];insertBefore(container,n,next);composed.splice(j,0,n);}}},
The text was updated successfully, but these errors were encountered:
Thanks for your patience and help tracking down these issues.
Yes, it looks like the issue is that removing the span from my-element and putting it into the fragment puts it in the fragment and then prompts my-element to distribute. When that happens, my-element assumes the span is still its responsibility and removes it. Your suggestion probably makes sense, thanks.
…e is where we expect it to be before removing it from its distributed position. We do this because the node may have been moved by Polymer.dom in a way that triggered distribution of its previous location. The node is already where it needs to be so removing it from its parent when it's no longer distributed is destructive.
https://jsbin.com/yejizipile/edit?html,console,output
different path from #2311
for what it's worth, my temp fix is to always check in _updateChildNodes/shady.html if the real parentNode is the container. See code below.
The text was updated successfully, but these errors were encountered: