Re: [csswg-drafts] [css-images-4] Color stop fixup: do interpolation hints function as positioned color stops? (#3931)

The CSS Working Group just discussed `Color stop fixup: do interpolation hints function as positioned color stops?`, and agreed to the following:

* `RESOLVED: Make spec match browsers on color hints / positions`

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Color stop fixup: do interpolation hints function as positioned color stops?<br>
&lt;AmeliaBR> github: https://github.com/w3c/csswg-drafts/issues/3931<br>
&lt;fantasai> AmeliaBR: This issue brought up with someone trying to implement gradients with color-hint syntax<br>
&lt;fantasai> AmeliaBR: His interpretation wasn't matching what browsers do<br>
&lt;fantasai> AmeliaBR: Issue is to clarify algorithm in spec to match what browsers do<br>
&lt;fantasai> AmeliaBR: All the browsers, or at least majority, all do the same thing<br>
&lt;fantasai> AmeliaBR: This has to do with color stops<br>
&lt;fantasai> AmeliaBR: color-stop consists of color and position<br>
&lt;fantasai> AmeliaBR: position can be implicit<br>
&lt;fantasai> AmeliaBR: evenly divide between known positions<br>
&lt;fantasai> AmeliaBR: color hints are different htough<br>
&lt;fantasai> AmeliaBR: color hints affect ???<br>
&lt;fantasai> AmeliaBR: Pave the cowpath / match reality request<br>
&lt;fantasai> TabAtkins: While I find the behavior is slightly weird<br>
&lt;fantasai> TabAtkins: but would have agreed with issue author initially<br>
&lt;fantasai> TabAtkins: Since everyone agrees, let's just spec that<br>
&lt;AmeliaBR> s/???/the allocation of implicit stop positions/<br>
&lt;fantasai> florian: Curious about what's weird about it, but if we have interop, doesn't really matter<br>
&lt;fantasai> TabAtkins: Weird because hint isn't a color stop, it is just a hint about how to interpret colors between<br>
&lt;fantasai> TabAtkins: So find it odd that it would affect positions, but eh.<br>
&lt;fantasai> AmeliaBR: Purpose was to adjust easing between adjacent stops<br>
&lt;fantasai> AmeliaBR: But because hint is expressed as a fixed position, there's interpetation that it's a position value<br>
&lt;fantasai> AmeliaBR: Same person that opened this opened another issue about other ways to talk about gradient easing<br>
&lt;fantasai> AmeliaBR: That's an interesting way of eventually creating a more logical approach in the future<br>
&lt;fantasai> AmeliaBR: while not conflicting with current browser implementations<br>
&lt;fantasai> AmeliaBR: so are interesting length issues if ppl want to follow up<br>
&lt;fantasai> florian: I'm sold<br>
&lt;fantasai> Rossen_: Anyone else?<br>
&lt;fantasai> Rossen_: Objections?<br>
&lt;fantasai> RESOLVED: Make spec match browsers on color hints / positions<br>
&lt;fantasai> AmeliaBR: One more point: editors are Tab, fantasai, Lea<br>
&lt;fantasai> AmeliaBR: Interested in making edits or should I draft up?<br>
&lt;fantasai> TabAtkins: I can do edits, but if you want to draft something happy to review/accept<br>
&lt;AmeliaBR> Scribenick: AmeliaBR<br>
</details>


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

Received on Wednesday, 22 May 2019 16:27:35 UTC