Status: Started Owner: [email protected] CC: [email protected] Labels: Type-Bug Pri-2 OS-Linux Area-WebKit Size-Small
New issue 10665 by [email protected]: Font fallback should eventually fall back on fontconfig http://code.google.com/p/chromium/issues/detail?id=10665 WebKit generally manages font fallback (consider CSS rules), so when it requests a font by name we should not allow fontconfig to do font fallback. However, if it finds no matches at all, we ought to allow fontconfig to do its best effort at matching. This is conceptually simple but the APIs involved (webkit, skia, etc.) make it difficult. agl suggested in bug 9100 that FontCache::getLastResortFallbackFont() could pass a magic font name so that skia could know to do this behavior. This bug is a tightening of bug 9100. I have a patch (contributed by Dan Erat) for this. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
