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
This sort of manipulation of the DOM isn't really supported and is likely to cause trouble. I'm not sure this is technically a regression.
The fix is to have another level of "tearItAllDown" ... one for the nodelist to call, where it doesn't matter if the DOM is in the page or not. Another one for the DOM Mutation callback where it checks if the node is still in the page.
When can-dom-mutate reports that a node has been removed, we first check whether the node is still in the document before tearing down its bindings.
Fixes#460
When can-dom-mutate reports that a node has been removed, we first check whether the node is still in the document before tearing down its bindings.
Fixes#460
As of can-stache-bindings 4.2.4 (with this change), bindings don’t work when an element is moved in the DOM like this:
Demo: https://codesandbox.io/s/m4ny5z8ovx
I’ve used
on:input:value:bind
just as an example, but this bug is not specific to that kind of binding.The text was updated successfully, but these errors were encountered: