htmx

i just wanted to show how effective cssnano + compression is

it will be a great day when we can hook this in to https://demo.htmx.org

wrt. components, we decided to provide all three ways (class, attribute, tag) but one problem is selector explosion. if we select a heading inside a card, that makes 18 selectors

```css
.missing-card, missing-card, [missing-card] {
    & :--heading {
        color: red;
    }
```

```css
.missing-card h1,missing-card h1,[missing-card] h1,.missing-card h2,missing-card h2,[missing-card] h2,.missing-card h3,missing-card h3,[missing-card] h3,.missing-card h4,missing-card h4,[missing-card] h4,.missing-card h5,missing-card h5,[missing-card] h5,.missing-card h6,missing-card h6,[missing-card] h6 {
        color: red;
    }
```

and it's all cached after the first download

if the aksimsek gambit can work in hyperscript, we can have a few selectors in missing.css

I think if you keep it around 10k, that's great, but it could be as big as bootstrap

I'm more concerned about not needing to hack up HTML than file size

https://cdn.jsdelivr.net/npm/bootstrap@5.1.3/dist/css/bootstrap.min.css

I'd say build first, optimize later.  Once you have a working prototype, check to see if the explosion looks like it's gotten out of hand.  My guess is that limiting the number of selectors won't affect the compressed download size that much.  If it does, then we can always choose the best one (or two) methods for selectors.

But until selector explosion gets out of hand and is either 1) hard to manage while developing, or 2) measurably affects the size/speed of the library -- I'd say don't worry about it.  No need to prematurely optimize.

Agree. But easy for me to say, I'm not the one that has to keep 37 selectors straight 😅

https://github.com/bigskysoftware/missing/blob/master/Contributing.md

One thing I really appreciate is how you constantly refer to the HTML spec, so I think we should think about doing is linking to the spec to justify particular decisions (hacker news enters the chat)

I have a spec link at the start of each file in `src/elements/`

```
/***
 4.4 Grouping content
 https://html.spec.whatwg.org/multipage/grouping-content.html
 ***/
```

it still needs a lot of work but it works pretty nicely i think