- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Feb 2024 21:57:02 +0000
- To: public-css-archive@w3.org
@tabatkins But then, what if you wrote `@apply --foo(..., var(--arg1))`? One might expect that this would be using the `arg1` from the mixin since the value is inserted in the mixin. But somehow it would track it's from outside and not get replaced inside the mixin. I dunno, I guess it's pretty confusing to me that some `var(--***)` will be resolved in the mixin, while others will be resolved after the mixin, on the element itself. It's pretty difficult to keep track of that. Maybe habit would make it easier, but I'm not sure. I mean, I totally get that it could be implemented that way by treating var(--*) different in the mixin depending on whether the name refers to an argument or an "using" import, but it's needlessly complicated. I'm still strongly in favor of a clean `arg(--arg1)` vs `var(--outer-var1)` where the behavior is always consistent per function. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1939658543 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 February 2024 21:57:05 UTC