- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Apr 2019 21:31:19 +0000
- To: public-css-archive@w3.org
I have various complaints about the high-contrast stuff: * The ability to override user preference using `high-contrast-adjust` that @MatsPalmgren has objected to in the past. * The dependency between high-contrast-adjust and basically all the color properties means that it's yet another property that needs to be cascaded early, which is not fun (probably wouldn't be a blocker though). * I find the `@media` block thing extremely weird / over-complicated. If we want to go that route, we also need to handle `<link media="">`, `<style media="">`, `@import url(...) <media>`, and all dynamic changes to those via the OM or attributes. I think implementing that properly is going to be a huge pain, and it really feels overkill for such a feature. I personally would prefer a simpler solution. Regarding @FremyCompany's proposal of using `revert`, we probably would still need the extra priority to determine whether the value is `auto` anyhow, since we don't have the concept of cascaded values vs. computed values, we compute as we do the cascade. But it's the same complexity as the other model, and `revert` would respect user stylesheets (though again the first model condition about UA sheet could be made to respect user stylesheets as well). -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3807#issuecomment-481873079 using your GitHub account
Received on Wednesday, 10 April 2019 21:31:21 UTC