- From: edbaafi via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Feb 2025 22:44:42 +0000
- To: public-css-archive@w3.org
[Loirooriol](https://github.com/Loirooriol) thanks for the references, I will go through them. I was trying to follow this discussion which is in so many threads and it was mentioned somewhere (including alluded to in this post's title) that the MVP would be inline only (value vs block). That's all I meant by "so far". Will look at the other proposals and see how far they are. > Tokens are discussed in CSS Syntax and, more relevantly for this topic, in CSS Variables. Ok not sure why my google search for `site:https://csswg.org "empty token stream"` didn't find a reference to that but will take a look. Thanks, I think I get the point about the block version being an `@` rule e.g. `@if`and being outside of the ruleset. Somewhere in this thread someone showed an `@if` that was inside of the ruleset's declaration block, and it created its own declaration block. I guess that stuck with me. With CSS nesting creating declaration blocks within declaration blocks, I guess it didn't read it as so off. > nothing prevents us from adding @if in the future with whatever syntax we want. At-rules and functions are completely distinct. Sure, I would argue for avoiding using the same name for a value function as an `@` rule for all the reasons I'm arguing against using `if` in a way that diverges from its use in many programming languages. Just because the language separates the `@` and `function()` namespaces doesn't mean it's a good idea to use the same name in both. But if this direction is set, than it's set. Again thanks all for pushing this regardless of my issues with the naming. -- GitHub Notification of comment by edbaafi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2679841481 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 February 2025 22:44:43 UTC