stephen / cssc Goto Github PK

Probably want:

• passthrough mode
• loose transform mode (warnings allowed)
• strict transform mode (warnings emitted as errors)

as an example, to handle case-insensitive attributes, probably we just emit a warning. it doesn't make sense to emit all the possible combinations (for case) for the value. the author can:

• passthrough for browsers that support it
• loose: get warned about them
• strict: get errored on them

The highlighter doesn't do a great job of truncating the error down if the line an error occurs on is too long.

I think locations only show up for qualified rules and nothing else. See: 3a5f098

If that's the case, we could probably save lexer/parser memory and time by not recording those locations.

Some things are missing:

• @supports syntax support: we could inline the content and put it in a @supports block
• media queries support: we could inline the content and put it in a @supports block

See notes here: https://www.w3.org/TR/mediaqueries-4/#mq-min-max about < and >. We may want to inc/decrement by .001 and do the same transform.

Add test/support for parsing 2n-1 (and an+b microsyntax in general)

It:

• does not follow cascade rules (and probably can't?)
• deletes the declaration / var() but probably should keep them
• maybe should warn if non-:root variables are there?