- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 May 2022 21:25:27 +0000
- To: public-css-archive@w3.org
I have to say, even when it was me that brought up the keyword solution, it is my least favorite. I am split between option 1 and 2. Option 1 allows reusing known gradient functions syntax and combines it with `<1d-image>` values. So, as @LeaVerou expressed it, we get the gradient controls for free. And any addition to the gradient functions or `<1d-image>` automatically works everywhere. For me, the big downside of this solution is that it reuses gradient terminology, which seems somewhat incorrect to me. Option 2 is guided by gradient syntax but adds its own functions. This makes them semantically correct. And it still allows authors to define them in a similar way as gradients. But the big downside here is that the syntax regarding the color stops is not the same because the meaning of thickness is different from the positioning syntax for color stops in gradients. And another downside is that existing functions and data types are not reused. So, any additions to them also require some updates to those functions. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7244#issuecomment-1115385341 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 May 2022 21:25:28 UTC