- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 26 Mar 2026 00:30:41 +0000
- To: public-css-archive@w3.org
> What if & > figure could get --arg as a token stream, same as an unregistered property, and resolve it locally? Yes, this is exactly what we're trying to avoid in the general case. It is what you get if you have an untyped argument. (In other words, *because* we lean on custom properties to actually do the technical lifting for us, you get the exact same behaviors, benefits, *and drawbacks* of using typed and untyped custom properties yourself. That's a *known* space for authors, and they can debug and fix problems the same way in Mixins that they do today when using custom props manually.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13727#issuecomment-4130725614 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 March 2026 00:30:42 UTC