- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Apr 2025 19:57:01 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-values-5] Accept more than 2 values in `*-mix(<progress>, ...)` and `progress()` notations``, and agreed to the following: * `RESOLVED: Update color-mix() to accept N arguments.` <details><summary>The full IRC log of that discussion</summary> <fantasai> TabAtkins: This was about allowing more than 2 values to be mixed together.<br> <fantasai> TabAtkins: resolution from https://github.com/w3c/csswg-drafts/issues/6245#issuecomment-2685746280 addresses this request<br> <oriol> q+<br> <astearns> ack oriol<br> <fantasai> TabAtkins: Will need edits to colors to allow color-mix() to have more than 2 values<br> <fantasai> oriol: When we were discussing what value should be with multiple values<br> <fantasai> oriol: Lea was saying you would pick the two values and interpolate them<br> <fantasai> oriol: another option would be weighted value among all values<br> <fantasai> oriol: I'm not sure how these map<br> <fantasai> TabAtkins: mix() all do weighted average, and map() does chained interpolation pairs<br> <fantasai> ChrisL: Not totally clear that I understand about chained pairs<br> <fantasai> ChrisL: color-mix() says if you don't specify either you have 50%<br> <fantasai> ChrisL: you want to allow more than 2?<br> <fantasai> ChrisL: if none is specified, you divide 100% by number?<br> <fantasai> lea: yep<br> <fantasai> ChrisL: Specify some but not all?<br> <fantasai> TabAtkins: Split remainder among unspecified ones<br> <fantasai> lea: and scale down sums above 100%<br> <fantasai> ChrisL: will need to expand tests<br> <fantasai> lea: expand but not change<br> <TabAtkins> fantasai: should we keep this open to track edits for color-mix()?<br> <fantasai> astearns: objections to updating color-mix() to match the plan for other mix() functions?<br> <fantasai> RESOLVED: Update color-mix() to accept N arguments.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11530#issuecomment-2770541161 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 April 2025 19:57:02 UTC