Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695)

I like the spirit of this and would probably choose your [prototype implementation](https://github.com/rooseveltframework/teddy/) over "native templates" if the latter turns out to be just another template language. Or I would probably use `<p>${actual_avascript}</p>` for maximum expressivenes, but I agree that HTML templates should look like HTML to gain the edge. I just wanted to remark that HTML is supposedly case insensitive and so your engine only works because you've implemented a custom parser. You would probably choose attribute *values* over names.

```html
<if test="caseSensitiveVariable">
  <p text="caseSensitiveVariable"></p>
</if>
<else>
  <p>the variable is not populated!</p>
</else>
```

I also got rid of the final `{curlybraces}` like that. But yes, I could see myself choose a simple feature set if the syntax was proportionally simple, so this.

-- 
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/695#issuecomment-341703635