W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2021

Re: [csswg-drafts] [css-color-adjust] Re-add `only` to mean "don't auto-adjust me", per WebKit's behavior (#5089)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 May 2021 16:42:53 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-844279182-1621442571-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-color-adjust] Re-add only to mean "don't auto-adjust me", per WebKit's behavior`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-color-adjust] Re-add only to mean "don't auto-adjust me", per WebKit's behavior<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5089#issuecomment-840840562<br>
&lt;dael> TabAtkins: There's some details which I don't have clarity on exactly behavior of 'only' keyword. Something about surpressing auto-darkening. Since I don't have great details and browsers aren't trying to ship force darkening I prop punt to L2<br>
&lt;dael> smfr: Even though not in Safari it is in the mail app and we consider css to cover non-browsers. only is UA should not apply auto colora djustment to content.<br>
&lt;chrishtr> q+<br>
&lt;dael> smfr: One of the issues spec doesn't address is color scheme and forced color interaction. Interesting on how color scheme should interact with forced colors and can authors opt out of forced colors<br>
&lt;dael> fantasai: Do have a property to opt out<br>
&lt;fantasai> https://www.w3.org/TR/css-color-adjust-1/#forced-color-adjust-prop<br>
&lt;dael> smfr: We do but separate. I think need mind-meld of color scheme, color adjust, and forced color adjust and I don't htink spec teases it out<br>
&lt;dael> TabAtkins: We prefered to say don't merge, they're separate, and treat them as such. I think that's the next issue<br>
&lt;dael> smfr: I guess I'd like to hear from an impl that has both to understand how they interact<br>
&lt;astearns> ack chrishtr<br>
&lt;dael> chrishtr: Chromium has both. I believe they don't interact<br>
&lt;dael> chrishtr: Some chromium browsers to have auto-dark mode that's use controlled. Ex Samsung internet. Comtent opting out is important where auto-darkening doens't work well<br>
&lt;dael> TabAtkins: Alright, was under assumption there wasn't anything out there. We should address. I'd ask smfr to provide more details on how this works so we can add a spec<br>
&lt;futhark> q+<br>
&lt;dael> TabAtkins: Would like to know what things cause dark and light to happen, the whole shebang so we can write a spec for it<br>
&lt;dael> smfr: There's a URL for original proposal we implement.<br>
&lt;smfr> original proposal on which color-scheme is based: https://github.com/w3c/csswg-drafts/issues/3299<br>
&lt;astearns> ack futhark<br>
&lt;dael> futhark: WE also have opt-out of forced in Android. We use meta tag presence as a way to opt out for web view apps<br>
&lt;astearns> ack fantasai<br>
&lt;Zakim> fantasai, you wanted to answer smfr's question<br>
&lt;dael> fantasai: Answering about interaction. If you have forced color and can determine if it's light or dark we force color scheme to be that. Color scheme and MQ get changed by forced colors. Color scheme does not caused forced color to do anything<br>
&lt;dael> smfr: Forced color always wins?<br>
&lt;dael> fantasai: Yes and changes color sheme to match<br>
&lt;dael> smfr: Only way to opt out is forced-color-adjust property?<br>
&lt;dael> fantasai: Yeah<br>
&lt;dael> astearns: So we'll continue to discuss and not punt?<br>
&lt;dael> TabAtkins: Yeah<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5089#issuecomment-844279182 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 May 2021 16:43:17 UTC

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