Re: [WICG/webcomponents] [declarative-custom-elements] Capabilities needed and open questions (Issue #1009)

There are some web components that may contain quite a bit of HTML, and aren't even guaranteed to appear more than once on the page.

Consider how much html is behind [this period table](https://codepen.io/mikegolus/pen/OwrPgB), for example.  Expand the pug to generate the full html to see what I mean.  Other examples:  Calendars, Calculators, Chessboards.

So not supporting this would double the payload.

I also think it makes quite a bit of sense when writing to HTML to "define" the HTML markup for something, previewing what you are generating as you type, then give it a name, and reuse it, similar to defining a variable when coding.  That's what [my POC](https://github.com/bahrus/be-definitive) was meant to convey.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1009#issuecomment-1526048908
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1009/1526048908@github.com>