[css-cascade-6] `supports()` for `@import` should accept a top-level `<supports-condition-name>`

[cdoublev]

CSS Cascade 4-6 define supports() for @import as accepting <supports-condition> | <declaration> with <supports-condition> pointing to CSS Conditional 3, which only defines <supports-decl>.

Is it an oversight or intentional? Major browsers have supported selector(), font-format(), font-tech(), for some time.

[ExE-Boss]

CSS Conditional 3’s <supports‑condition> includes <supports‑feature>, which is extended by newer CSS Conditional specs:

• CSS Conditional 3 § 6. Feature queries: the ‘@supports’ rule
• CSS Conditional 4 § 2. Extensions to the ‘@supports’ rule
• CSS Conditional 5 § 2. Extensions to the ‘@supports’ rule

[cdoublev]

Ah, that is right. There is no <supports-condition> to point to in CSS Conditional 5.

I was misled by the absence of <supports-condition-name> in supports(<supports-condition> | <declaration>), which is what I wanted to point out in this issue, actually.

I am updating the title and tags accordingly.