[Webkit-unassigned] [Bug 140290] [GTK] Pixelated fonts used for Engadget headline

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=140290

--- Comment #14 from Martin Robinson <mrobinson at webkit.org> ---
(In reply to comment #13)
> (In reply to comment #10)
> > fc-match won't give proper results because it matches in a different way
> > than WebKit. WebKit will walk down the font list until it matches a font
> > with the same name.
> 
> So what do we do when no font named Segoe UI exists? Why do we not want to
> use the same fonts that would be selected by fontconfig?

CSS has stricter rules about selecting fonts than fontconfig. Presumably page authors have a better idea of what fonts work with their page, so we give their font list priority, fist trying to find an exact match on the CSS list before falling back.

The details of our approach, which is follows Chromium's strategy can be found in Source/WebCore/platform/graphics/freetype/FontCacheFreeType.cpp.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150112/ee672245/attachment-0002.html>