- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jan 2023 21:18:59 +0000
- To: public-css-archive@w3.org
@plinss That other solution was discussed in #4748, even initially approved in https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-960145492, but reverted in https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-1233176065. IIRC the concern was that it uses 2 levels of indentation, which can be inconvenient when having multiple levels of nested rules. I guess I would prefer it over option 3 (which yeah, I feel like it's bending the language too much for little gain), but postponing the brackets instead of nesting them (i.e. option 4) avoided the double indentation so it was probably better. @jensimmons I don't doubt that there are some people doing this kind of things, but I lack numbers to know if these are only some anecdotical cases, or if the breakage of adding a feature mixing symbols with declarations would be huge. Also, there might have been people using `--` to comment out a declaration, but this didn't prevent custom properties since the effect is not observable unless you use `var()` or JS APIs. So I'm not convinced that adding such new features is "very likely off the table" as Tab said. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1379496526 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 January 2023 21:19:01 UTC