Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
emilio opened this issue May 31, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@emilio
Copy link
Collaborator

commented May 31, 2018

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

@squelart

This comment has been minimized.

Copy link

commented May 31, 2018

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

@frivoal

This comment has been minimized.

Copy link
Collaborator

commented Jun 1, 2018

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

@tabatkins

This comment has been minimized.

Copy link
Member

commented Jun 1, 2018

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

@frivoal

This comment has been minimized.

Copy link
Collaborator

commented Jun 3, 2018

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

This comment has been minimized.

Copy link
Member

commented Jun 3, 2018

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

@frivoal

This comment has been minimized.

Copy link
Collaborator

commented Jun 4, 2018

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

This comment has been minimized.

Copy link
Member

commented Jun 4, 2018

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"...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.