- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 20:25:05 +0000
- To: public-css-archive@w3.org
@romainmenke I don't think I understand what you are trying to do. I don't see what that achieves, and I'm not sure the logic is quite right. But I also think we need to agree on the most useful CSS behavior, before we spend too much time worrying about how to polyfill it? Currently, selectors at the top level of a CSS document are not 'relative' to anything. They can't, for example, start with a combinator. Nested selectors are relative to the parent selector. Relative selectors often start with a combinator: ```css > h2 { /* not a valid selector */ } main { > h2 { /* nesting makes it valid, with implied `&` */ } } ``` The first selector here is currently invalid if we apply the stylesheet directly. Would it suddenly become valid when the stylesheet is imported with nesting applied? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11756#issuecomment-2686113510 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 20:25:07 UTC