[mediaqueries-4] [mediaqueries-5] Spec no longer mentions case-insensitivity.

[emilio]

Not sure it's intentional... Perhaps should be noted, at least regarding media features and such?

[squelart]

And following @emilio's #2726, if case-insensitivity is re-added, please specify that it's ASCII -- unless it really shouldn't be.

[frivoal]

@tabatkins Are we getting it for free somehow through referencing css-syntax, or is this an actual omission?

[tabatkins]

You get it for free via Values & Units, actually.

[frivoal]

V&U defines that keywords behave like that, but it seems to me that the way it is phrased scopes it to property values, and that's now what we are discussing here.

I wound expect this to be handled somewhere in css-syntax as part of the tokenizer, but I don't know how that specs work very well, so maybe this expectation is misplaced.

[tabatkins]

It definitely can't happen at the Syntax level, or else <custom-ident>/etc couldn't be case-sensitive.

[frivoal]

If necessary, I'm happy to add this in the mq spec, but redundant normative prose isn't good, so I want to make sure we're not covered already. If we are, a note is enough, if not, we should add normative prose.

If you think we are good thanks to V&U already, please explain how, 'cause I don't see how that statements covers us.

[tabatkins]

Ah so actually, at the rule level (which is what MQ defines), it is indeed Syntax that wins, via its section on extending the CSS Value Definition Grammar to rules: https://drafts.csswg.org/css-syntax/#rule-defs.

Per this, tokens are compared ASCII case-insensitive. (Tho, uh, I should make sure that says "unless otherwise specified"...)