/* Before */
header a:hover, main a:hover, footer a:hover { color: var(--brand); }
/* After */
:is(header, main, footer) a:hover { color: var(--brand); }
The difference between them is specificity
:is() takes on the specificity of its most specific argument; :where() always has zero specificity, no matter what's inside it. That makes :where() genuinely useful for writing default styles that are trivially easy to override later:
:where(h1, h2, h3) { margin-top: 0; } /* easy to override, on purpose */
Where we've started using them
Long, repetitive selector lists in our base stylesheet have shrunk noticeably. It's a small change with an immediate, visible readability win - the kind of CSS addition that doesn't need a big announcement to be worth adopting right away.
Two selectors that solve the same problem, differently
:is(header, main, footer) a { color: navy; }
:where(header, main, footer) a { color: navy; }
Both let you group selectors instead of repeating a rule three times, which alone is worth adopting. The difference that matters: :is() takes on the specificity of its most specific argument, while :where() always carries zero specificity, no matter what's inside it.
Why the specificity difference is the actual feature
Zero-specificity :where() rules are trivially easy to override later with a single class, which makes it the right choice for base styles and resets you expect other rules to layer on top of. Reach for :is() when you want the grouped selector to carry real weight in the cascade, and :where() when you're deliberately writing something meant to be overridden without a fight.