Re: [csswg-drafts] `<absolute-color-base>` not enough anymore (#9555)

As described in the op/title, this issue may be considered as fixed, but I see two related issues that may need to be further discussed separately:

  - `device-cmyk()` in `@font-palette-values/override-colors` (suggested in the op)
  - colors resolved at used value time or later in `color-mix()` (implemented in Chrome/FF)
  - colors resolved at used value time or later in RCS (implemented in Chrome, and FF for `currentcolor`)

I cannot find any related issue open.

| Non-absolute color in | `color-mix()` | RCS       | `override-colors`
| --------------------- | ------------- | --------- | -----------------
| `currentcolor`        | Chrome/FF     | Chrome/FF | invalid
| `<system-color>`      | Chrome/FF     | Chrome    | invalid
| `light-dark()`        | Chrome/FF     | Chrome    | invalid
| `contrast-color()`    | NA            | NA        | NA
| `device-cmyk()`       | NA            | NA        | NA

*Specs currently require all non-absolute colors to be `invalid` in `color-mix()`, RCS, `override-colors`.*

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9555#issuecomment-2817148558 using your GitHub account


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

Received on Sunday, 20 April 2025 12:29:10 UTC