CSS quiz: The color of the h2 is…

(with native CSS, no preprocessor like Sass).

```
<div>
<h2>A heading</h2>
</div>
```

```
div, #cssisawesome {
h2 {
color: red;
}
}

div h2 {
color: blue;
}
```

red
33.3%
blue
64.9%
black (initial)
1.8%
Poll ended at .

@matuzo I will continue to vote for these all based on what I think it should be, even if I know that it's different.

In this case, I also know why it is (ahem) the way that it is, and I guess I sort of kind of agree but not really. They could have chose then Sass way of expanding the selectors.

@AmeliaBR @matuzo Didn’t the Sass way lead down the road of “combinatorial explosion”?
@keithjgrant @matuzo Yes, in Sass, but that's less an issue if you aren't actually expanding, you're just calculating the specificity of the selector matched against a particular element.
@AmeliaBR @keithjgrant @matuzo would it be useful/confusing/utter chaos to have an opposite of :is() that returns the lowest specificity? Not :where that returns 0, but the lowest within the list... Which could still be zero anyway.

@alvaromontoro @AmeliaBR @keithjgrant @matuzo I guess we could get some syntax sugar for `:is(<lowest specificity>, :where(<higher specificity>…))`.

This made me think about how `clamp()` is syntax sugar for `max(MIN, min(VAL, MAX))`, but then my mind digressed and I started thinking about a “specificity clamp” which is absurd (e.g. set the lowest and highest specificity — totally impractical).