- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 May 2024 12:43:55 +0000
- To: public-css-archive@w3.org
> Or, if we keep it as a function, perhaps we can relax the restriction to "only one of these per declaration"? So that one could do things like: We had literally this exact case today, with the gradient interpolation that we wanted to resolve into a “space” when it is not supported. Having an ability to use the `first-supported()` inside the value would be great. I guess the main issue with this will be that it should be invalid as a value for non-registered custom properties, so there won't be a way for the authors to specify two instances of it in the runtime? Or we will be ok with making the declaration invalid at computed-value time when we encounter the second instance of the `first-supported()` in some declaration? -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5055#issuecomment-2135127774 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 May 2024 12:43:56 UTC