- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jun 2021 17:32:00 +0000
- To: public-css-archive@w3.org
Oh yeah, the production I was proposing should definitely go in Color, I didn't realize that was ambiguous. Though it may need to be Color 4, as [that's where interpolation is defined](https://drafts.csswg.org/css-color-4/#interpolation). I think something like: ``` <color-interpolation> = in <color-space> [ <hue-interpolation> ]? <hue-interpolation> = shorter | longer | increasing | decreasing | specified ``` If we want that kind of granularity, we should add the entire `<color-interpolation>` syntax to `<color-stop-hint>`, not just a part of it. This way people can also customize the color space the transition happens in. Hence the production would become: ``` <linear-color-hint> = <length-percentage> || <color-interpolation> ``` Note that there should still be a `<color-interpolation>` param in the first argument of gradients, to cover the vastly more common case of wanting to specify an interpolation strategy for the entire gradient. > It looks like the hue-interpolation keyword is placed after or between colors I had not actually realized this, this is new edit. I …don't think this should be the case. This is an argument for the _interpolation_, not an argument for the _color_. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6369#issuecomment-857893638 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 June 2021 17:32:46 UTC