New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users
Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2010
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug
M-5

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
Linux font fallback should choose appropriate "style" of font
Project Member Reported by mattm@chromium.org, Feb 4 2010 Back to list
What steps will reproduce the problem?
1. Use chromium on fresh ubuntu install, which doesn't have non-free fonts 
installed.
2. Visit page which doesn't specify any fonts or which specifies the non-
installed fonts.
3. (Also, open font options and see what fonts it has fallen back to 
there.)

What is the expected output?
Fonts should fallback to appropriate types (arial -> sans, times new roman 
-> serif, courier new -> monospace)

What do you see instead?
Everything falls back to Sans.



Please use labels and text to provide additional information.

 
chromium-sans.png
45.1 KB View Download
chromium-with-fonts.png
35.0 KB View Download
simple.html
285 bytes View Download
Comment 1 by mattm@chromium.org, Feb 4 2010
Labels: Area-Internals
Comment 2 by evan@chromium.org, Mar 22 2010
Labels: -Pri-2 Pri-3 Mstone-5
Status: Assigned
This used to work.  I wonder what broke.
Comment 3 by evan@chromium.org, Apr 2 2010
Can you attach your test page?  I think this actually does work, or is a dup of issue 
31287.
Comment 4 by mattm@chromium.org, Apr 2 2010
It's the first attachment
Comment 5 by f...@sofaraway.org, Apr 2 2010
fresh install of Ubuntu Lucid, monospace is broken. It looks fine in the fonts UI though (.

Screenshot attached: Chromium ToT / Firefox ToT

It's difficult to read logs or anything formated in these conditions.
Is this the same bug?
Screenshot-Fonts and Languages.png
35.8 KB View Download
fixed-fonts.png
42.5 KB View Download
Comment 6 by f...@sofaraway.org, Apr 2 2010
another example here:
chbug.png
199 KB View Download
Comment 7 by evan@chromium.org, Apr 2 2010
Labels: -Pri-3 Pri-1
Wow, this looks really bad.  I'll take a look at it immediately.  I bet I wrote a bug 
in my last change or something.
Comment 8 by evan@chromium.org, Apr 2 2010
Status: Fixed
Fixed in WebKit@r57027, will be pulled in during the next WebKit update (hopefully 
this afternoon, possibly next week).
Project Member Comment 9 by bugdroid1@chromium.org, Oct 12 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 10 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Internals-Skia -Area-Internals -Mstone-5 Cr-Internals-Skia M-5 Cr-Internals
Project Member Comment 11 by bugdroid1@chromium.org, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Sign in to add a comment