[w3c/webcomponents] [templates] API for updating (#685)

I'm happy to see that updating existing DOM is accounted for (and fully specced!) in this model. It was never really clear to me how that would work, from previous discussions.

However, I think we might be able to come up with a better surface API.

In particular, I think it's weird that you essentially end up using `TemplateInstance` for two different things. First it holds your nodes with all the values stamped out. Then it transitions to a new phase of its lifecycle where you don't care about its children, but instead just care about using its update() method as an indirect path to talk to its former children.

I'm not sure what a better API would look like, at least tonight. I'll try to noodle on it before TPAC. But I think the current design is a little weird.

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