Re: [w3c/webcomponents] Add an updated proposal for DOM Parts. (#899)

> Once thing that's not entirely clear to me is what the internal model of a part is and why having it is beneficial other than developer ergonomics. Does this enable any performance wins over mutating the tree yourself, for instance?

Another big win for template libraries and hand-written DOM code is the cloning behavior. This would be the first way to clone some kind of _reference_ to nodes, along with a subtree.

-- 
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/pull/899#issuecomment-716731792