- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Nov 2024 08:26:51 +0000
- To: public-css-archive@w3.org
Is it possible to edit Cascade 4 and 5 to prevent `w3c/reffy` from extracting [`<import-conditions>`](https://drafts.csswg.org/css-cascade-5/#typedef-import-conditions), which would be removed by this PR in Cascade 6? ```diff - @import [ <url> | <string> ] ... <import-conditions> ; - <import-conditions> = [ supports( [ <supports-condition> | <declaration> ] ) ]? <media-query-list>? + @import [ <url> | <string> ] ... [ supports( [ <supports-condition> | <declaration> ] ) ]? <media-query-list>? ; ``` --- Is it possible to define `<supports()>` and `<media()>` in Conditional 5, and `<scope()>` in Cascade 6, to avoid duplicate/overlapping definitions? For example, `supports()` is defined differently in [CSS Values 5](https://drafts.csswg.org/css-values-5/#typedef-if-test), [Conditional 5](https://drafts.csswg.org/css-conditional-5/#funcdef-supports), Cascade 4/5. `<supports()>`, `<media()>`, `<media-query-list>`, would define the import conditions. ``` @import [ <<url>> | <<string>> ] [[ layer | layer(<<layer-name>>) ] || <scope()> || <supports()> || <media()>]? <<media-import-condition>>? ; <scope()> = scope( [ <scope-selector> | <scope-start> ]? ) <supports()> = supports( [ <supports-condition> | <declaration> ] ) <media()> = media( <media-query-list> ) ``` `<scope-selector>` would be defined below the definition of `@scope` with `@scope <scope-selector>? { ... }`. At least, the grouping brackets no longer seem necessary around `scope()`, now that it is implicitly optional. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11237#issuecomment-2505521838 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 November 2024 08:26:52 UTC