[moritzwarhier]

I see what you mean, but what would this do except add more churn?

Words sometimes have misleading aspects, but I don't see any practical problem with the current usage of the word "selector" in web dev. The CSS part is often omitted when it's implicit.

The spec separates selectors cleanly into its own module already, and there are already implementations that don't rely on HTML rendering.

Any rename by commitee wouldn't stick anyway, and the origin of this selector spec is CSS, doesn't prevent other uses.

When you bring in "cascading", you already go close to the CSS / rendering aspect, because that's the most common use case for cascading?

Selectors don't cascade, rules do.