Re: [csswg-drafts] [css-conditional-3]: Inconsistent phrasing around placement of @import rules (#5697)

I hadn't read "Any `@import` rules must precede all other valid at-rules and style rules in a style sheet (ignoring `@charset`)" from https://drafts.csswg.org/css-cascade-5/#at-import. It's not totally obvious that a "style sheet", used there, is a different thing from a `<stylesheet>`, used as the content of the at-rules, but also seems clear enough that I'm happy to close that part of the issue.

I think my second paragraph, about https://drafts.csswg.org/css-conditional-3/#use, is less resolved.
Having read that bit of css-cascade, I now think that the second paragraph of https://drafts.csswg.org/css-conditional-3/#use is redundant with it since [the conditional rules are at-rules](https://drafts.csswg.org/css-conditional-3/#processing), and "Any `@import` rules must precede all other valid at-rules". [`@namespace`](https://drafts.csswg.org/css-namespaces-3/#syntax) has similar wording in its spec. [`@charset`](https://drafts.csswg.org/css-syntax-3/#charset-rule) is unique and ... not actually a rule anymore ... but already defined not to follow anything else. If there are rules that are only restricted relative to style rules but not at-rules, this paragraph would still have an effect, but it could then benefit from a different set of examples. Maybe replace it with a note?

I'm happy to dial into the 9 Dec telecon.

-- 
GitHub Notification of comment by jyasskin
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5697#issuecomment-736914928 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 December 2020 00:50:26 UTC