- From: Steinar H. Gunderson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Oct 2022 13:34:30 +0000
- To: public-css-archive@w3.org
> Dropping it and just using CSSStyleRule is definitely possible, however. The big issue is just that you wouldn't preserve whether a style rule was written with https://github.com/nest or not (unless we add some additional state to CSSStyleRule), so a rule like @nest & > .foo {...} would probably serialize down to just & > .foo {...}. (I think that's fine, fwiw.)
Yes, I would say so, too. Especially with the syntax now seemingly going in the direction of supporting many more explicit things. It seems odd to me to have a special rule type whose _only_ difference is that it serializes with @nest in front; if so, I'd prefer simply having a flag somewhere? But just serializing to the shortest possible form seems better to me.
--
GitHub Notification of comment by sesse
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7831#issuecomment-1271602174 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 October 2022 13:34:31 UTC