- From: Michael C. via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Sep 2021 09:42:54 +0000
- To: public-css-archive@w3.org
> So, put simply, if, within rule braces, the parser encounters another opening brace, combinator, or ampersand (which isn't part of the value for a declaration), it should then go into selector parsing mode, instead of declaration parsing? > > Interesting. I guess any preceding declaration values need to be capped off with a semicolon, to avoid a comma as a combinator being confused with being part of a value. I think what we're talking about here is dropping the ampersand entirely in favor of curly braces wrapping any nested selectors. Keeps the syntax simpler—no need for both `&` _and_ `@nest &` support. -- GitHub Notification of comment by proimage Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-927271547 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 26 September 2021 09:42:56 UTC