- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jul 2024 23:56:19 +0000
- To: public-css-archive@w3.org
> This has the same issue as many other proposed separators, now else: is invalid in other properties (including custom properties). No, it's fine as long as it sits in the condition position of the grammar. It's just a special condition, spelled `else`, that always matches. It doesn't interact with the grammar of the value part at all. `if(foo(): first value, else: second value)` > I don't understand what you mean. Omit what, how? Can you write an example? If you don't want a value, you can just not write a value, like `if(foo(): , else: a value)`. That's first value part is perfectly reasonable, it's just empty. > So can we please stop suggesting lengthy function names and separators? Right, thus `if( [ <condition> ':' <decl-value>? ]# )`. Don't think it's possible to get any shorter/simpler. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2237789319 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 July 2024 23:56:20 UTC