- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Tue, 19 Aug 2025 13:25:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-cascade-6] When using @import scope(), are the imported styles 'nested'?`, and agreed to the following: * `RESOLVED: Close no change` <details><summary>The full IRC log of that discussion</summary> <emilio> miriam: we decided to add `@import ... scope()` to scope entire sheets<br> <emilio> ... in the draft andruud wrote that imported sheets that are scoped, the selectors at the root don't become nested style rules<br> <emilio> ... meaning relative selectors at the top level not work<br> <emilio> ... we discussed that root level relative selectors should still be disallowed, that doesn't make nested relative selectors allowed now<br> <emilio> ... there's been some back and forth<br> <emilio> ... on the one hand we want to import a scope and behave more or less the same, but we don't want relative selectors at the root<br> <emilio> ... I don't think we want them to be allowed conditionally on how you import these<br> <emilio> ... with that and how we decided that `&` was `:where(:scope)`<br> <emilio> ... and when imported they can write `&`<br> <emilio> ... so we might want to close no change<br> <emilio> matthieud: you can wrap the stylesheet on `& {}`<br> <emilio> astearns: other questions / comments?<br> <emilio> RESOLVED: Close no change<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11756#issuecomment-3200763924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 August 2025 13:25:49 UTC