[w3c/webcomponents] Extensible template parts (#810)

During the F2F @JanMiksovsky and @justinfagnani brought up some use cases for being able to create your own parts, that the browser would still be responsible for to clone. E.g., having a way to deal with JavaScript properties.

It'd be interesting to know the exact use cases and requirements around this. What kind of information does such a part need to carry that the browser would be responsible to clone? Can we avoid cloning requiring executing JavaScript? Etc.

(Not saying we need this feature for v0 by the way, but it's good to know where folks want to take it as it might influence the design.)

-- 
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/810