- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Mar 2022 09:53:34 +0000
- To: public-css-archive@w3.org
> This does suggest one potential compromise: if CSS adjusted the syntax of <boolean-condition> to ensure it doesn't and never will conflict with a valid Sass boolean expression (a straw example would be surrounding it with square brackets), we could just suck up the usability pain of issue 1 above and parse both in parallel. My feeling though is that this would be much weirder from the perspective of a CSS user than simply using @when. Personally I would find a syntax like `@if test(<boolean-condition>)` less of an eyesore then `@when/@else` - a function that returns a boolean is a familiar construct, and I believe this would meets the criteria required for dual-parsing? -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1072250093 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 March 2022 09:53:35 UTC