Re: [w3c/webcomponents] Expose "cloning steps" to custom elements (cloneCallback) (#176)

I was considering trying [`domc`](https://github.com/Freak613/domc) out (one of the fastest libraries in the [Krause JS Framework Benchmark](https://stefankrause.net/js-frameworks-benchmark8/table.html) due in part to use of `cloneNode`), but my fear is that domc's use of `cloneNode` might cause errors or bugs due to missing JS properties in cloned custom elements.

Maybe Custom Elements could use something like `cloneOutputCallback` and `cloneInputCallback`: `cloneOutputCallback` returns some thing (f.e. an object containing state) from a custom element being cloned, and `cloneInputCallback` on the new custom element receives the output of the cloned node's `cloneOutputCallback` in order to place that state back where it belongs inside the cloned custom element?

-- 
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/176#issuecomment-466844177