[Webkit-unassigned] [Bug 19161] wrong font size when css font-family includes monospace

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 22 14:14:00 PDT 2009


ojan at chromium.org changed:

           What    |Removed                     |Added
                 CC|                            |hyatt at apple.com

------- Comment #10 from ojan at chromium.org  2009-04-22 14:13 PDT -------
Talked to hyatt on IRC. We came to the conclusion that we should match FF
behavior to maximize compatibility. To be clear, this means we only use the
fixed-width font-size if the font-family is set to *exactly* monospace. For
font-family:'monospace', font-family:foo,monospace and
font-family:monospace,foo, we should use the standard font-size.

Longer-term we should test a webkit build that has one font-size for all fonts
and see how bad the compat hit is. If it's minor, then we can consider getting
rid of the font preferences entirely for Safari/Chrome. According to Hyatt,
noone especially wants these preferences. They are just leftovers from Netscape
long ago that everyone matched for compatibility.

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

More information about the webkit-unassigned mailing list