- From: L. David Baron <dbaron@dbaron.org>
- Date: Fri, 30 Aug 2013 11:11:41 -0400
- To: Simon Pieters <simonp@opera.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <20130830151141.GA1166@crum.dbaron.org>
On Friday 2013-08-30 12:35 +0200, Simon Pieters wrote: > [[ > User agents must support these keywords, but should map them to > "default" values, not based on the user's OS settings (for example, > mapping all the "background" colors to white and "foreground" colors > to black). > ]] > -- http://tabatkins.github.io/specs/css-color/Overview.html#system-colors I tend to think this "should" isn't a good idea. For a start, the system colors are still needed along with 'appearance', given the way appearance is actually (interoperably, I think) implemented. (Was the disagreement between the likely-interoperable implementations and the spec part of why it got dropped from css-ui, post CR?) I don't think Gecko would be able to honor this should, both because we need the correct values in our UA style sheets and because we need them in our UI. (That said, Gecko also has a number of longstanding prefixed extensions to address issues such as those raised in http://lists.w3.org/Archives/Public/www-archive/2013Aug/0027.html The working group removed these additions from the spec, I believe because it wanted to deprecate the entire set.) > Using just black and white seems unnecessarily boring. It's also not > so clear which ones are backgrounds and which are foregrounds. There's a clear separation between foregrounds, backgrounds, and borders. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Friday, 30 August 2013 15:12:19 UTC