Intent to Ship: Add Remaining Predefined Color Spaces as Interpolation Spaces

Aaron Krajeski

unread,

Feb 24, 2025, 9:36:56 AMFeb 24

to blink-dev

Contact emails

Explainer https://developer.mozilla.org/en-US/blog/css-color-module-level-4/
Specification https://www.w3.org/TR/css-color-4/#predefined

Summary

Display P3, Rec2020, ProPhoto RGB and a98 RGB are specified in CSS color 4 as predefined color spaces but had not yet been implemented as color spaces for interpolation. Other UAs have already implemented.

Blink component Blink>CSS

TAG review None

TAG review status Not applicable

Risks

Interoperability and Compatibility

None

Gecko: Already implemented. See https://codepen.io/mysterydate/pen/azbzvqB in Firefox.

WebKit: Already implemented. See https://codepen.io/mysterydate/pen/azbzvqB in Safari.

Web developers: https://issues.chromium.org/issues/382086298

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes

Is this feature fully tested by web-platform-tests? Yes

Flag name on about://flags None

Finch feature name None

Non-finch justification None

Requires code in //chrome? False

Estimated milestones

M134

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None

Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5350873536135168?gate=5081273527435264

This intent message was generated by Chrome Platform Status.

Mike Taylor

unread,

Feb 24, 2025, 9:53:51 AMFeb 24

to Aaron Krajeski, blink-dev

Would you mind requesting the various review gates (privacy, security, enterprise, etc) in your chromestatus entry? Thanks.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d1e3e07b-ac7b-449f-b9b9-dc91d515ee6fn%40chromium.org.

Yoav Weiss (@Shopify)

unread,

Feb 25, 2025, 2:58:36 AMFeb 25

to blink-dev, Mike Taylor, Aaron Krajeski

Thanks for catching us up here!!

On Monday, February 24, 2025 at 3:53:51 PM UTC+1 Mike Taylor wrote:

Would you mind requesting the various review gates (privacy, security, enterprise, etc) in your chromestatus entry? Thanks.

On 2/24/25 9:36 AM, 'Aaron Krajeski' via blink-dev wrote:

Contact emails
aar...@chromium.org

Explainer https://developer.mozilla.org/en-US/blog/css-color-module-level-4/
Specification https://www.w3.org/TR/css-color-4/#predefined

Summary
Display P3, Rec2020, ProPhoto RGB and a98 RGB are specified in CSS color 4 as predefined color spaces but had not yet been implemented as color spaces for interpolation. Other UAs have already implemented.

Blink component Blink>CSS

TAG review None

TAG review status Not applicable

Risks

Interoperability and Compatibility
None

Gecko: Already implemented. See https://codepen.io/mysterydate/pen/azbzvqB in Firefox.

WebKit: Already implemented. See https://codepen.io/mysterydate/pen/azbzvqB in Safari.

Web developers: https://issues.chromium.org/issues/382086298

How do you envision developers using this while supporting older Chromiums?

Other signals:

WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Debuggability
None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes

Is this feature fully tested by web-platform-tests? Yes

Flag name on about://flags None

Finch feature name None

Non-finch justification None

Requires code in //chrome? False

Estimated milestones
M134

Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None

Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5350873536135168?gate=5081273527435264

This intent message was generated by Chrome Platform Status.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

Aaron Krajeski

unread,

Feb 25, 2025, 11:24:22 AMFeb 25

to blink-dev, Yoav Weiss (@Shopify), Mike Taylor, Aaron Krajeski

For the record, feature detection/fallback can work thusly:

https://codepen.io/mysterydate/pen/zxYKReo

If the user sets a valid gradient, then attempts to set with one of the new color spaces but those are not yet available, the CSS background property will not be set.

Aaron Krajeski

unread,

Feb 25, 2025, 11:27:19 AMFeb 25

to blink-dev, Mike Taylor, Aaron Krajeski

> Would you mind requesting the various review gates (privacy, security, enterprise, etc) in your chromestatus entry? Thanks.

Done

一丝

unread,

Feb 25, 2025, 10:30:55 PMFeb 25

to blink-dev, Aaron Krajeski, mike...@chromium.org

In previous versions of Chrome, I found that although `in srgb` was specified, the color stops would take effect as long as display-p3 was specified in color stops. Other browsers seem to convert to srgb first.

So which behavior is CSS specification compliant?

```css

background: linear-gradient(to right in srgb, color(display-p3 1 0 0), green);

```
Demo: https://codepen.io/yisi/pen/jEOMXex

Daniel Bratell

unread,

Mar 5, 2025, 10:19:46 AMMar 5

to Aaron Krajeski, blink-dev, Mike Taylor

It seems the enterprise gate got stuck so you may want to look at that one.

LGTM1 - the work to get out of our comfortable srgb sandbox will take a while, but I appreciate that one more step is taken. I'm also not concerned with temporary incompatibilities since I think they are unlikely to break functionality. (Please correct if I'm wrong!)

/Daniel

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d3960993-b363-4e20-9f01-64d655673da8n%40chromium.org.

Mike Taylor

unread,

Mar 5, 2025, 11:03:52 AMMar 5

to Daniel Bratell, Aaron Krajeski, blink-dev

LGTM2

Yoav Weiss (@Shopify)

unread,

Mar 11, 2025, 8:57:29 AMMar 11

to blink-dev, Mike Taylor, Daniel Bratell, Aaron Krajeski

LGTM3

Please make sure that the fallback is documented somewhere where developers can find it (e.g. MDN)

LGTM2

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

Reply all

Reply to author

Forward