- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 May 2017 08:48:39 +0000
- To: public-css-archive@w3.org
Yes, I believe there is potential on this topic, and that we should address it. However, I do not believe it to be very simple. Primarily because `high-contrast` means different things in different OSes and UAs, to which authors should react differently: * First axis * Contrast-boost via image processing at the pixel level (possibly done by the OS with no understanding of the content) * Content-aware contrast-boost, which may pick different (contrasty) colors for different types of content, treats images differently from text, could affect which font or font-weight is used (necessarily done by the UA) * Second axis: Is the contrast boost coupled with a color inversion (which can be done at the pixel level, or content aware to avoid inverting images), or with enforcing dark-on-light or light-on-dark (which assumes an understanding of what's content and what's background). So, do we need 2 (or 12) completely separate queries to express all the various things that exist? 1 query with a bunch of values? Expose some higher level semantics? How? I've heard ideas on this topic, and have a few of my own, but I don't think we have firm conclusions yet. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1286#issuecomment-298306558 using your GitHub account
Received on Monday, 1 May 2017 08:48:46 UTC