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
In certain cases elements pushed to a list that is rendered with each stay in the DOM even if the parent element has been removed (interestingly enough all wrapping DOM will be gone as well). Using a template like:
<div>
{{#data}}
<p>This is the item:</p>
{{#item}}
{{#each subitems}}
<divclass="item">
{{test}}
</div>
{{/each}}
{{/item}}
{{/data}}
</div>
Hey @justinbmeyer I took a look at this bug a little bit and the item does call nodeLists.register, although I'm not sure what that actually achieves as far as node removal. The first item gets removed through live.html's makeAndPut function. Should both items be removed at that time?
In certain cases elements pushed to a list that is rendered with
each
stay in the DOM even if the parent element has been removed (interestingly enough all wrapping DOM will be gone as well). Using a template like:And this component:
The fragment for the dynamically added
Pushed item
will remain in the DOM after calling.removeAttr('item')
.Fiddle demonstrating the issue: http://jsfiddle.net/Cjsqz/1/
The text was updated successfully, but these errors were encountered: