Re: [csswg-drafts] [css-color] `color-interpolation` inherited property to set default interpolation space (#7035)

The CSS Working Group just discussed `[css-color] color-interpolation inherited property to set default interpolation space`.

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-color] color-interpolation inherited property to set default interpolation space<br>
&lt;emeyer> Github: https://github.com/w3c/csswg-drafts/issues/7035<br>
&lt;emeyer> Lea: We’re been going through spec and adding interpolation space in gradients, other things.  Don’t have a way to add to adnimations or mixing yet.<br>
&lt;emeyer> …When it comes to augmenting gradients, this will make them invalid in older browsers.  Authors would need @supports or variables.  It’s kind of tedious.<br>
&lt;chris> comparison of this proposal with the other one: https://github.com/w3c/csswg-drafts/issues/7035#issuecomment-1041850688<br>
&lt;chris> q+<br>
&lt;emeyer> …It also means any new spec with interpolation lacks control until we add this.<br>
&lt;JakeA> q<br>
&lt;emeyer> …There is no quick easy way for authors to say they want interpolation without dealing with browser issues.  So maybe a color-interpolation property would help here.<br>
&lt;JakeA> q+<br>
&lt;emeyer> …That way it can be set and inherited and overridden.  You can set it at root and all your gradients become better.<br>
&lt;emeyer> …Chris pointed out you probably want different interpolation spaces for different use cases.<br>
&lt;Rossen_> q?<br>
&lt;emeyer> chris: You may want different interpolations for different operations.  I can imagine you’d want different interpolations on different transitions.<br>
&lt;emeyer> …The question is, is it useful to set a default for an entire document or subtree.<br>
&lt;Rossen_> ack chris<br>
&lt;emeyer> …SVG has two properties that deal with this sort of thing.<br>
&lt;smfr> css filters are in sRGB<br>
&lt;emeyer> …I don’t think it adds enough value to justify the complexities.<br>
&lt;Rossen_> ack JakeA<br>
&lt;emeyer> JakeA: I have similar concerns.  You could set this property and it makes all the gradients look great, but then later we add it to mix-blend-mode or whatever and they all look ugly.<br>
&lt;Rossen_> ack fantasai<br>
&lt;emeyer> fantasai: If different interpolations for different operations are expected, it would make sense to have focused properties (color-interpolation-gradient, etc.).<br>
&lt;faceless> q+<br>
&lt;lea> +1 to almost everything fantasai just said (except re: in keyword)<br>
&lt;emeyer> …I also don’t think we should have an end keyword.<br>
&lt;fantasai> s/end/in/<br>
&lt;Rossen_> ack dbaron<br>
&lt;emeyer> dbaron: I was wondering about a global property: is it possible to have two global properties?  Is it the case that there’s a set of things that make sense to interpolate in linear light and another set of things that need gamma correction?<br>
&lt;fantasai> s/focused properties/focused longhand properties/<br>
&lt;emeyer> …Does it make more sense to have those two rather than seven or eight properties?<br>
&lt;emeyer> chris: I think that’s correct; some want to be linear and some want to be perceptual.<br>
&lt;Rossen_> ack faceless<br>
&lt;emeyer> faceless: I think this would be confusing if it didn’t include the SVG properties as legacy syntax.  I don’t see a reason we couldn’t do that.<br>
&lt;TabAtkins> +1 to Chris and Jake's concern about a single global default<br>
&lt;emeyer> Rossen: Sounds like there’s an interest in exploring this in terms of focused properties like color-interpolation-gradient, which is safer.  Is that the path we want to take?<br>
&lt;emeyer> chris: I think there’s interest in further exploration.<br>
&lt;TabAtkins> But I'm fine with longhands like fantasias mentioned<br>
&lt;lea> s/fantasias/fantasai/<br>
&lt;emeyer> Rossen: Let’s take the conversation back into the issue.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7035#issuecomment-1041903366 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 16 February 2022 17:21:41 UTC