- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 May 2019 14:50:55 +0000
- To: public-css-archive@w3.org
> We described this last year in #3299, which is still open. Indeed, it does look like that original intent (color scheme transformations at least) was lost in translation. Ah, you're referring to "If the user's preference does not match something in the list, the UA is allowed to apply transformations to the content (e.g. apply high-contrast)." from Simon's post. If that's the extent of it, opting the page into [forced-colors mode](https://drafts.csswg.org/css-color-adjust/#forced), then that's fine, it's just a separate feature that's technically orthogonal to this. But if y'all are planning on doing something *separate from* forced colors, *please* actually describe it in a new issue so we can talk about it. We're trying our best to make sure these features are described accurately and fully, so authors can have a reasonable idea of how their pages will look. If the "same" feature ends up still acting substantially differently between browsers, then there's no point to it being standardized at all. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3881#issuecomment-490113295 using your GitHub account
Received on Tuesday, 7 May 2019 14:50:57 UTC