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

There doesn't seem to be much appetite from implementers. Needs more compelling use cases to be reconsidered.

The lack of parity with built-in elements was considered (e.g., script and input), but we're not convinced those are not mistakes (apart from template, which we're okay with being a special snowflake).

-- 
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-370306017

Received on Monday, 5 March 2018 04:22:05 UTC