- From: andruud via GitHub <noreply@w3.org>
- Date: Fri, 20 Mar 2026 12:42:27 +0000
- To: public-css-archive@w3.org
@cdoublev Let's see if we should do a follow-up here, since I left your comment hanging ... > 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? What bad situation would arise if we don't do this? Accidentally linkage to an obsolete dfn? > Is it possible to define `<supports()>` and `<media()>` in Conditional 5, and `<scope()>` in Cascade 6, to avoid duplicate/overlapping definitions? That amounts to a normative change that goes beyond this PR? Granted, these things _should_ be consistent, but we don't have a resolution right now to change css-conditional-5 (`@when`, specifically). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11237#issuecomment-4097741495 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 March 2026 12:42:28 UTC