- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Nov 2023 22:05:20 +0000
- To: public-css-archive@w3.org
> Lea only listed this as a requirement for mixins, so I don't think there's any disagreement here. Ah, right, there was an explicit mention of "how functions work" so I presumed it was being suggested more widely. :+1: then. > And it's most often used to access flow control and loops, which we don't have at this point. More than that; I presume it would also need access to various things around string manipulation, etc, and the ability to interpolate strings into CSS constructs in various ways. In all, a *very* significant expansion of responsibility, for a substantially different use-case. So yeah, agreed, not appropriate to pursue at this point. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1806498703 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 November 2023 22:05:21 UTC