W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

[csswg-drafts] [css-color-adjust-1] Cascade within forced-colors MQ (#4178)

From: Melanie Richards via GitHub <sysbot+gh@w3.org>
Date: Tue, 06 Aug 2019 22:16:45 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-477618613-1565129804-sysbot+gh@w3.org>
melanierichards has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-color-adjust-1] Cascade within forced-colors MQ ==
Somewhat combinatorial between specs, but css-color-adjust-1, [Forced Color Schemes](https://www.w3.org/TR/css-color-adjust-1/#forced) might be the best place to put this.

It would be ideal if an author could override a [property value affected by forced colors](https://www.w3.org/TR/css-color-adjust-1/#forced-colors-properties) without requiring the author to set `forced-color-adjust` to `none` on the element.

In some cases, authors will want to fully manage how an element is styled in forced color modes, which is an appropriate use of `forced-color-adjust`. But in other cases, they may just want to change a singular property value without interfering with other UA forced color styles, e.g.:

```
@media (forced-colors: active) {
  [aria-disabled="true"] {
     color: GrayText;
  }
}
```

We should perhaps tweak cascade expectation in [Forced Color Schemes](https://www.w3.org/TR/css-color-adjust-1/#forced) such that cascaded values outside of the `forced-colors` media query are unset, but origin override rules apply when additional styles are set within a `forced-colors` media query block.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4178 using your GitHub account
Received on Tuesday, 6 August 2019 22:16:47 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:12 UTC