Re: [w3c/webcomponents] [templates] Maybe each {{ ~ }} should be its own text node? (#683)

How about the final DOM tree's state after the substitution had occurred? i.e. after each node template part's value had been assigned.

Normalizing text nodes in that case would result in some weird edge cases like some Text nodes in a node template part not being in the final DOM tree due to them getting merged together, or even some Text nodes end up having extra contents.

If we're going to that path, it might be actually better to use something like static range to represent each part instead of having a node list.

Also see https://github.com/w3c/webcomponents/issues/680.

-- 
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/683#issuecomment-341361574