- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 21 Aug 2014 14:05:46 -0700
- To: John Hudson <tiro@tiro.com>
- Cc: Behdad Esfahbod <behdad@google.com>, Cameron McCormack <cam@mcc.id.au>, John Daggett <jdaggett@mozilla.com>, www-style list <www-style@w3.org>, public-webfonts-wg <public-webfonts-wg@w3.org>
On Thu, Aug 21, 2014 at 1:40 PM, John Hudson <tiro@tiro.com> wrote: > On 21/08/14 1:21 PM, Behdad Esfahbod wrote: >> I'd rather CSS doesn't go down that path. CSS doesn't specify whether >> fonts should be hinted, use embedded bitmaps or not, render as subpixel, >> grayscale, etc. It's out of the scope IMO. > > > I'm in two minds on this. My first instinct was the same as Behdad's: that > this is a font rendering issue, and not an obvious candidate for CSS level > authoring control. However, we do expect CSS to be able to control colour > display of many page elements, including monochrome text. > > While I can see the point of John's proposed font-variant-color property, > I'm actually more interested in possible CSS interaction with colour font > technologies that enable user-defined colour values for polychromatic > glyphs. For example, the Microsoft CPAL table spec allows for user defined > palettes, and CSS seems to me an obvious place to provide for author > definition of colours. This seems easily addressable, if browsers are willing, by changing 'color' to accept a comma-separated list of values, which are used by multi-color glyphs in some defined order. ~TJ
Received on Thursday, 21 August 2014 21:06:35 UTC