1917523 - With (forced-colors: active) , using registered property, color declaration seems to be ignored and the inherited color is picked

Status: NEW

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Nicolas Chevobbe [:nchevobbe]]

Attachment: forced-color-registered-property.html

Steps to reproduce

1. Enabled forced-colors on your OS
2. Open attachement

Expected results

The first div (div - using registered custom property) color should be CanvasText

Actual results

color seems to be SelectedItemText

---

The only difference between the two divs is that one is using a registered property, and the other is not.
FWIW, in Chrome both divs have the same color

Comment 1

[Emilio Cobos Álvarez [:emilio]]

That is kind-of expected (if unfortunate), because we don't carry whether the color is a system color in the computed value.

So basically, when you specify --a: CanvasText;, we compute it to --a: rgb(0, 0, 0); (or the relevant color), and when we substitute it we see color: rgb(0, 0, 0);, which usually wouldn't work.

See https://github.com/w3c/csswg-drafts/issues/4915 and relevant bits. I guess per that the right thing to implement would be a color flag that kept whether it was a system color.