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
{{ message }}
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.
Enhancement
If you create a custom element then add children post creation, they are not consumed into the parent. We can achieve this using a MutationObserver to watch for child nodes.
The text was updated successfully, but these errors were encountered:
That would give us the changes, but another consideration is what to do with the DOM after that. Re-using DOM after the projector is created would be tricky I suspect, so it would be easier to detach those children from the DOM, generate the virtual DOM nodes necessary and then invalidate.
@kitsonk we already do those things via the DomWrapper. basically we just need to take the children nodes, wrap them and set them as children (we already do this at the initialisation phase)
Enhancement
If you create a custom element then add children post creation, they are not consumed into the parent. We can achieve this using a
MutationObserver
to watch for child nodes.The text was updated successfully, but these errors were encountered: