[webkit-dev] Font description + font family = redundancy?
joshchia at gmail.com
Wed Jun 18 16:22:22 PDT 2008
Since the AtomicString is one of the family items in the FontDescription,
why is it specified, i.e. why is the same family specified twice, once in
the FontDescription and once in the AtomicString? What are the functions
supposed to do with the family specified by the AtomicString in addition to
whatever they are supposed to do with the families specified in the
On Wed, Jun 18, 2008 at 3:14 PM, David Hyatt <hyatt at apple.com> wrote:
> You can specify multiple font families in a single CSS font declaration.
> Therefore a FontDescription can contain multiple families in a list. The
> AtomicString represents one of the families in the list.
> On Jun 18, 2008, at 5:04 PM, Joshua Chia wrote:
> I'm trying to understand the font-related code in
>> FontCache::createFontPlatformData() takes two arguments: a FontDescription
>> and an AtomicString specifying the family. Since FontDescription already
>> has family specified in it, why does createFontPlatformData() take the
>> AtomicString family argument? What do the two respective family
>> specifications in the FontDescription and the AtomicString mean for
>> createFontPlatformData? Isn't this some kind of redundancy? I have the
>> same question about FontCache::getCachedFontPlatformData().
>> Furthermore, FontCache::createFontPlatformData() calls
>> FontPlatformData::FontPlatformData(FontDescription, AtomicString), so I have
>> the same question about FontPlatformData::FontPlatformData().
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev