- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Tue, 31 Mar 2026 22:15:23 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-color] Why not just alias deprecated system colors at parse time?`, and agreed to the following: * `RESOLVED: Clarify that they "compute" to the other value. (But specified value remains as specified.)` * `ACTION: Also clarify that they're affected by color-scheme.` <details><summary>The full IRC log of that discussion</summary> <emilio> ChrisL: oriol suggested that since deprecated system colors are supposed to be the same, why not aliasing them?<br> <emilio> ... there seemed to be general agreement<br> <lea> emilio: Impl-wise it's possible but I think the reason why they're not parsed aliases to begin with in Gecko is we need them to resolve to different values<br> <lea> ... not a big deal, we can parse-alias them when parsing web content stylesheets, that's just the historical reason<br> <lea> ... we want to make a title bar match the system color, there's a few colors to represent an active titlte bar, if we want to un-deprecate them that changes behavior<br> <alisonmaher> q+<br> <lea> ... that's the only thing that may make parsed aliases more annoying, you'd write div.style.color = "activeCaption", but then it would not roundtrip<br> <lea> ... if we want to bring some of these back, we have to change behavior again<br> <lea> q+<br> <lea> main q is are there some of these we may want to bring back<br> <lea> ... but no objections<br> <emilio> ChrisL: ntim also explained some of the WebKit behavior<br> <emilio> ... something about using them internally<br> <emilio> emilio: so same thing as gecko, using them internally?<br> <emilio> ntim: just existing apps using these<br> <Rossen> ack fantasai<br> <emilio> fantasai: support the logic emilio articulated, I'd support more explicit writing in the spec saying that they compute to the same, but specified value should remain as specified<br> <emilio> ChrisL: we're explicit about it<br> <emilio> fantasai: it says "same as", not "it computes as"<br> <emilio> ... we should also clarify color-scheme affects this<br> <emilio> ChrisL: but it does<br> <emilio> fantasai: yeah agreed, just not super clear in the spec<br> <emilio> ... doesn't mention the color-scheme property at all<br> <Rossen> ack alisonmaher<br> <emilio> alisonmaher: I think if we do believe we might end up with some changes emilio's point is fair<br> <emilio> ... re the titlebar the current thing is the accentcolor keyword, it doesn't match the inactive state tho<br> <ChrisL> q+<br> <emilio> ... not sure the plan is using the deprecated colors tho<br> <emilio> emilio: fwiw for native titlebar appearance you do need the (windows) active system color<br> <emilio> ... but not a big deal<br> <Rossen> ack lea<br> <emilio> lea: I don't think authors expect perfect roundtrip when setting specified values, lots of colors behave like that<br> <Rossen> ack ChrisL<br> <fantasai> PROPOSED: Clarify that they "compute" to the other value. (But specified value remains as specified.)<br> <emilio> ChrisL: I see some arguments both ways but parse aliasing might be a bit annoying<br> <florian> +1<br> <fantasai> RESOLVED: Clarify that they "compute" to the other value. (But specified value remains as specified.)<br> <fantasai> ACTION: Also clarify that they're affected by color-scheme.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13459#issuecomment-4165909441 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 March 2026 22:15:24 UTC