-
Notifications
You must be signed in to change notification settings - Fork 5
disconnectedCallback and parentNode #12
Comments
This goes even further. The LayoutDependencyType needs to be updated when an element leaves or enters the DOM. Maybe we just update EVERYTHING when an element disconnects or connects? Or is that overkill? Maybe it only affects the layout behavior anyway. Or maybe not. There might be behaviors (e.g. signal) that search for events using a selector. It needs to be updated as well. |
What we basically need to do is to call |
Now the thing is that this should be a general purpose solution. Right now we have |
Now we're talking: if you create a new disconnected element-meister the behaviors will crash, since they expect the element to be connected. Luckily, there is a |
Currently we detach every single behavior when an element is disconnected. However, the dependency check uses el.parentNode. We should have a special mode for detaching/cleaning up everything. This is different from regular batch detaching.
The text was updated successfully, but these errors were encountered: