You cannot traverse the whole document with DocumentFragment and same with browser node API. But anyway, the motivation is why to read the DOM nodes from the br

You cannot traverse the whole document with DocumentFragment and same with browser node API. But anyway, the motivation is why to read the DOM nodes from the browser while I already have them in the app. I like to think about it as a layer that connects what's missing from any modern framework. See the effect in Drag & Drop. The great benefit of knowing exactly where the dragged element is going in the tree. The basic implementation is to `switch` with siblings in the same container. And perhaps do the same thing with the whole container. Being able to drag & drop containers with the same level/depth. Maybe later, expose the `switch` functionality so it can be replaced with `bounceToRight` or `JustHide`.. etc. I've been asked many times how this is different, and as far as I can tell it's not just simple implementation for draggable. Hope to reach the point where I can achieve a fully flexible layout. The Insertion and design can in theory done by the end-user. So much work has to be done Including add Svelte support. Edit: I've already started a project to compose flexible forms: https://github.com/jalal246/folo https://github.com/jalal246/folo And like DFlex the backbone is pure javascript.