Re: [csswg-drafts] [css-color-4] Clarify how to resolve `<system-color>` (#13719)

I think so. Thank you.

Regarding `<deprecated-color>`. I do not think its computed value is tested on WPT. If it was defined as a parse time alias of `<system-color>`, as suggested in #13459, this would change the declared/resolved value that can be observed in Chrome and Firefox today:

```js
const { style: declared } = target
const resolved = getComputedStyle(target)

declared.colorScheme = 'light'
declared.color = 'buttonborder'
declared.color // "buttonborder"
resolved.color // "rgb(0, 0, 0)"
declared.colorScheme = 'dark'
declared.color // "buttonborder"
resolved.color // "rgb(255, 255, 255)"

declared.colorScheme = 'light'
declared.color = 'activeborder'
declared.color // "activeborder"
resolved.color // "rgb(0, 0, 0)"
declared.colorScheme = 'light'
declared.color // "activeborder"
resolved.color // "rgb(0, 0, 0)"
```

This is the behavior suggested in the comment I already quoted in my previous comment:

  > Given that these are legacy values for legacy compat & we don't want authors using them in new content, we can probably safely define them all as light mode values

So do you want to postpone this question until #13459 is answered? Do you want me to open a separate issue? Or do you want to clarify it right away?

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


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

Received on Friday, 27 March 2026 05:07:55 UTC