WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
55935
System font fall back behavior
https://bugs.webkit.org/show_bug.cgi?id=55935
Summary
System font fall back behavior
Kenichi Ishibashi
Reported
2011-03-08 04:26:26 PST
See
http://crbug.com/62435
in more detail. In some ports, when a system font fallback is performed to render some Unicode characters such as PILE OF POO (U+1F4A9), WebKit renders the character by using the last resort glyph even if there are fonts which contain appropriate glyph for the character. It might be worth to render the character by using appropriate glyph if it possible. Here is some notes: - FireFox renders these characters appropriately even if the page doesn't specify font families for the characters. - As far as I checked, mac/win WebKit ports render the PILE OF POO by using the last resort glyph if system font fallback occurred. - Chromium linux port renders the character by using appropriate glyph (if it is available). I'd like WebKit folks' opinion about it.
Attachments
Add attachment
proposed patch, testcase, etc.
Avi Drissman
Comment 1
2011-03-08 07:09:20 PST
If there exists a valid glyph for a code point, it should be used. It might not fit typographically, but it's better than just having a box.
Skip
Comment 2
2011-08-26 16:46:34 PDT
Chromium on Linux doesn't properly handle many glyphs.
http://code.google.com/p/chromium/issues/detail?id=90940
Jungshik Shin
Comment 3
2011-11-02 13:00:05 PDT
I agree with avi on that. Browsers have to hunt down fonts to cover characters if there is a font to cover them instead of prematurely falling back to last resort glyph.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug