Re: [csswg-drafts] [css-color-adjust-1] Forced colors mode usage beyond high contrast mode (#6664)

The CSS Working Group just discussed `[css-color-adjust-1] Forced colors mode usage beyond high contrast mode`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-color-adjust-1] Forced colors mode usage beyond high contrast mode<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6664<br>
&lt;dael> Rossen_: Tagged by rune<br>
&lt;dael> Rossen_: Can anyone take this?<br>
&lt;dael> TabAtkins: fantasai and I can<br>
&lt;dael> TabAtkins: Question is how to reflect UA feature that does forced dark mode. Being tested on Android, I believe iOS has it<br>
&lt;smfr> only forced dark mode in apple mail, not in the browser<br>
&lt;dael> TabAtkins: Suggestion is reflect as a forced colors mode. Would imply we're doing things forced colors does<br>
&lt;dael> TabAtkins: Assuming auto-darkening does match up enough I think that's fine and we reflect that in prefers-color-scheme. Acts like author chose a11y feature to set colors to dark<br>
&lt;dael> TabAtkins: Seems straight forward. Doesn't give authors more things to react to. I suggest we accept Beverly's suggestion<br>
&lt;Rossen_> q?<br>
&lt;dael> Rossen_: Feedback?<br>
&lt;alisonmaher> q+<br>
&lt;dael> smfr: Not sure if auto-darkening and forced colors are same. There's a bunch we resolved on for forced colors that's a lot difference<br>
&lt;Rossen_> ack alisonmaher<br>
&lt;dael> alisonmaher: Haven't looked too much, but I don't think forced dark is same. I think it's paint time. Don't use system colors to force darkening. I don't hitnk impl would match as spec for forced colors<br>
&lt;dael> Rossen_: You're saying darkening is paint?<br>
&lt;dael> alisonmaher: Yes. haven't looked that much<br>
&lt;dael> smfr: That's true of what Apple did in mail<br>
&lt;dael> Rossen_: That's a pretty major difference in behavior. Not sure harmonizing the two makes sense<br>
&lt;alisonmaher> q-<br>
&lt;dael> TabAtkins: Enough difference that authors should react differently? Not sure. If similar enough people can act the same way and for auto-darken should change colors it's fine. If they should do other changes should use another MQ<br>
&lt;dael> Rossen_: Would adjust-color override apply to auto-darkening?<br>
&lt;dael> TabAtkins: I would assume it would<br>
&lt;dlibby> q+<br>
&lt;Rossen_> ack dlibby<br>
&lt;dael> dlibby: Regarding difference between featurs a lot of authors will writed forced-color MQ and use system colors. With forced dark mode being at paint time it could lead to some inconsistencies. Seems hard to map the two concepts directly<br>
&lt;fantasai> +1 to not linking this with forced-colors mode<br>
&lt;dael> Rossen_: Feedback I'm hearing is that even though conceptually there are similarities it doesn't necessarily mean it will be gray-dark or green-dark or whatever in order to match the paint time effects<br>
&lt;dael> Rossen_: I think we should take it back to the issue and do more work there<br>
&lt;dael> Rossen_: Sound reasonable?<br>
&lt;dael> TabAtkins: Yep<br>
</details>


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


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

Received on Wednesday, 6 October 2021 23:43:58 UTC