[Webkit-unassigned] [Bug 36548] New: Wrong font instantiated from an unknown font family

[bugzilla-daemon at webkit.org]

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

           Summary: Wrong font instantiated from an unknown font family
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: olivier at tilloy.net


Created an attachment (id=51532)
 --> (https://bugs.webkit.org/attachment.cgi?id=51532)
layout test case

According to the CSS fonts specification
(http://www.w3.org/TR/css3-fonts/#font-family-the-font-family-property), "[the
font-family property] specifies a prioritized list of font family names or
generic family names", and "authors are encouraged to append a generic font
family as a last alternative for improved robustness".

If a font family in the list doesn't match any known font on the system, the
next family in the list should be used. The current implementation in WebKitGTK
seems to always find a match for the first family in the list (falling back to
the generic font family if necessary), whether it matches an actual existing
font or not. Consequently, other families in the list are never given a chance
to render the text as intended.

Consider the attached layout test case: it can reasonably be assumed that
"UnknownFontFamily" doesn't match any known font on the system, therefore the
text should be rendered using the second family in the list, Courier, which is
a monospace font. Instead it is rendered using the generic family, serif.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.