Re: [w3c/webcomponents] Bulk property updates (#718)

@JanMiksovsky:

> But the core of this proposal isn't about a better way to updating childNodes, it's looking for a better way to updating multiple aspects or an element or a tree of elements.

This is the way any virtual DOM library works today, and that object representation that you just mentioned is what we call a vnode (e.g.: https://github.com/snabbdom/snabbdom/blob/master/src/vnode.ts#L13-L37), and libraries can do what they please via some simple abstraction.

Another questions is about nested element, and what to do to with `childNodes`, and the potential conflicts between that and `textContent`, who gets applied first? who wins?

@rniwa:

>  there is definitely a benefit to having an ability to bulk apply DOM mutations at once.

I think you can do that today with a very simple abstraction using some virtual DOM library principles.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/718#issuecomment-352606614