New issue 108645 by rmnet....@gmail.com: "font-family": Local font shows
odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
Chrome Version : 18.0.983.0
OS Version: OS X 10.6.8
URLs (if applicable) : http://lifevaluesinventory.org
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Chrome (16.0.912.63): OK
Safari 5: OK
Firefox 4.x: OK
IE 7/8/9: OK
What steps will reproduce the problem?
1. Install a web font locally. I'm using "Museo Sans" with is free from
FontSquirrel.com (I imagine you can do the same with a font from Google Web
Fonts).
2. Create an HTML page and add a "font-family" property that references the
*local* name of that font *first* and then the online version *second*.
ex: font-family: "Museo Sans", "MuseoSans500", sans-serif;
3. Load the page in Canary (18.0.983.0).
What is the expected result?
- The local version of the font will be used (so a font download from the
server isn't necessary) and look like readable text, not wacky characters.
What happens instead?
- The local version of the font is garbled and shows weird characters (see
attached screenshot).
- Canary must not realize the text is garbled, because it doesn't fall back
to the online version.
- When I remove the reference to the local version, Canary uses the online
version and looks fine.
ex: font-family: "MuseoSans500", sans-serif;
Additional Notes
- I think there's a been a slight regression of:
<http://code.google.com/p/chromium/issues/detail?id=72727>
- Originally, that bug (72727) wasn't using the local version of the font
at all and wasn't falling back to the next font in line (in this case, the
online version). Instead, it would display the text as Times New Roman.
- Eventually that was fixed and Canary was working fine. I just tested this
again the other day against a site and testcase that I'd used to test 72727
against and I saw these weird characters. So I think some new bug has been
introduced into the same system that was going funny in 72727. Only this
time, instead of Times New Roman, it's something a bit worse :-)
- You can download MuseoSans500 from
<http://www.fontsquirrel.com/fonts/Museo-Sans>. I didn't attach it here
because I wasn't sure about licensing.
- I've attached screenshots (Testcase: normal size + enlarged, example
site) and my testcase (the first and second line of text should use the
same font).
Attachments:
Chrome-font-face-bug-testcase.html 1.2 KB
Screen shot 2011-12-26 at 12-26, 12.04.09PM.png 37.2 KB
Screen shot 2011-12-26 at 12-26, 12.04.23PM.png 53.4 KB
Screen shot 2011-12-26 at 12-26, 12.16.22PM.png 26.8 KB
Re-uploading the screenshot of the example website
<http://lifevaluesinventory.org>.
Attachments:
Screen shot 2011-12-26 at 12-26, 12.39.22PM.png 599 KB
Comment #2 on issue 108645 by jer...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
* Does this work correctly with a nightly build of Safari
(http://nightly.webkit.org/) ?
* Does the problem go away if you launch Chrome with the --no-sandbox
command line flag?
- Tested in Webkit r103679 (December 26, 2011): OK (no bug).
- Started Canary *with* "--no-sandbox": OK! The local font loads as it
should.
That's great!
What does that mean?
Related: Issue 29729 - "Chrome sandbox blocks loading of fonts stored
outside stock system locations"
<http://code.google.com/p/chromium/issues/detail?id=29729>
Not sure if it was really fixed though. Lots of references to other bugs,
including Issue 72727, which is where this issue comes from.
I have the same very annoying problem.
To reproduce, install Droid Serif with FontExplorer, restart Chrome, tada!
Attachments:
Screen Shot 2012-01-06 at 10.42.59 AM.png 59.3 KB
Forgot to say, the site in question is
http://www.typografie.info/2/showthread.php/25172-Versal-%C3%9F-in-Adobe-Illustrator-Indesign-etc-CS4-aufw%C3%A4rts
Comment #8 on issue 108645 by tha...@google.com: "font-family": Local font
shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
(No comment was entered for this change.)
Comment #9 on issue 108645 by yu...@chromium.org: "font-family": Local font
This really needs to get more attention! Having the very basic content
accessible is more important than any speed improvements, new features or
whatever. I wouldn't care so much if it was the wrong font, but it's
completely unreadable.
As an professional designer, I have quite a few fonts, and I can't read any
text if an website is using any of them!
I tried to reproduce the bug with 18.0.983.0 and 18.0.1016.0 on MacOS
10.7.2, but I couldn't see the bug. Does this bug still happen?
Bashi: I think this bug is related to the interaction of font management
software (in DieBuche's case FontExplorer) and the Mac sandbox. Such
software allows you to install fonts from an arbitrary location on disk.
We have code in place to side-load fonts that are blocked by the sandbox
via the browser but it looks like the code isn't kicking in in this case, I
need to look more closely to figure out what's going on.
Jeremy: I see. Thank you for the information.
Still happening for me with 10.7.2 and 18.0.1010.0 dev
All other browsers are fine and the the only font software I have installed
is Fontcase (http://www.bohemiancoding.com/fontcase)
Issue 113834 has been merged into this issue.
Has anyone tried a manual fix like moving the font location of their
managed font library?
I use the latest FontExplorer and I got the same problem (Safari works fine
here).
Same problem for me and all web-designers in my office.
Chrome: 18.0.1025.142
We've found that ONLY when our google web fonts are activated in Font
Explorer X 3.1.1, do our sites look broken. As SOON as we deactivate, the
sites look perfect (with their google web fonts)
This problem didn't start happening until either yesterday, March 29th or
today, the 30th.
Comment #23 on issue 108645 by ba...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
Looks like this could occur on SnowLeopard (e.g. issue 121351 and issue
108645) now. I'll take a look.
s/issue 108645/issue 120929/
This definitely looks a bug that cropped up in Chrome 18, which was just
released in the stable channel a few days ago.
I just confirmed that it persists in Chrome Canary 20.0.1089.0 as well, on
OS X 10.6.8.
Found the following feedback that seems related:
Report# 235485128
18.0.1025.142 (129054)
Mac OS X 10.7.3
Attachments:
garbled.png 187 KB
Comment #34 on issue 108645 by ba...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
@thakis -- thank you for reminding me that. We create SkTypeface from
FontPlatformData::ctFont() in
Source/WebCore/platform/graphics/skia/FontSkia.cpp, but
FontPlatformData::ctFont() doesn't point to the correct NSFont* when we
load the font from the browser process. I'm preparing the fix.
BTW, during the investigation, I realized that there are some problems with
out-of-process font loading.
- In the browser process, we call IO functions from a thread that disallows
IO:
http://code.google.com/searchframe#OAMlx_jo-ck/src/content/common/mac/font_loader.mm&exact_package=chromium&q=font_loader.mm&type=cs&l=110
This causes crashes when we use debug build.
- If we deactivate a font which was loaded by using OOP loading, and then
activate it again, CTFontGetPlatformFont() in
FontLoader::LoadFontIntoBuffer() returns NULL. This causes renderer crashes
as the result of hitting NOTREACHED() in
RendererWebKitPlatformSupportImpl::SandboxSupport::loadFont().
We should fix them too. (I'll do it later)
To reiterate:
playmobil@ wrote code to ipc text from the browser process to the renderer
process
i guess that code isn't getting used in skia
so the sandbox makes font loading fail
skia needs to use that codepath
See e.g.
http://codereview.chromium.org/2811013
http://codereview.chromium.org/2804001
https://bugs.webkit.org/show_bug.cgi?id=41148
http://codereview.chromium.org/7080024
for a few places where the old infrastructure was introduced
same issue here... version 18 of chrome.. started with the use of
FontExplorer X Pro... going to try uninstalling FontExploder... Huge fail
on the part of Chrome
Re: My comment 54 and Fontcase.
I've since reinstalled the latest version of Fontcase via AppStore and the
problem has not reoccurred. So in my case, I think it was just that I had
an older version of this font manager.
Odd browser behavior [ver 18.0.1025.152]: I received notification to
restart chrome and the font problem was worked out; then I refreshed and
the odd characters reappeared. Then a few minutes later they disappeared
and fonts were OK. Now - in two instances of the same page running within
Chrome, one is fine and the other is garbled text.
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=131324
------------------------------------------------------------------------
r131324 | ba...@chromium.org | Sun Apr 08 19:41:13 PDT 2012
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_message_filter.cc?r1=131324&r2=131323&pathrev=131324
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/common/mac/font_loader.mm?r1=131324&r2=131323&pathrev=131324
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/common/mac/font_loader.h?r1=131324&r2=131323&pathrev=131324
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/common/sandbox_mac_fontloading_unittest.mm?r1=131324&r2=131323&pathrev=131324
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_message_filter.h?r1=131324&r2=131323&pathrev=131324
M
http://src.chromium.org/viewvc/chrome/trunk/src/content/renderer/renderer_webkitplatformsupport_impl.cc?r1=131324&r2=131323&pathrev=131324
Mac: OOP font loading should run on FILE thread.
FontLoader calls file_util::GetFileSize() and file_util::ReadFile(),
which should be called from the file thread, but FontLoader runs on the
io thread now. Make it run on the file thread.
BUG=108645
TEST=none
Review URL: http://codereview.chromium.org/9950141
------------------------------------------------------------------------
I use google web fonts on my own web site. Attached is the garbled mess
that is displayed today in Chrome.
Attachments:
Screen shot 2012-04-09 at 2.43.11 PM.png 338 KB
Issue 121675 has been merged into this issue.
Comment #67 on issue 108645 by ba...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
Issue 122658 has been merged into this issue.
Is this going to go into the v18 line soon? Chrome is often unusable now
(I'm having to revert to Safari for many websites that use Google web fonts
and for Gmail for emails coming from rich text mail clients like Outlook).
Many emails from business contacts are unreadable in Chrome until this is
fixed.
Is there a known workaround for people that use font management
programs? "Stop using them" isn't a valid workaround since the font files
have already been moved around on the filesystem. Neither is "Turn them
off" for the same reason. I saw mention of "--no-sandbox" but that is
obviously undesirable because that opens up vulnerabilities.
I agree with the previous post. I'm not very technical so a technical work
around is it going to be of any help to me. To make matters worse my entire
business runs on google apps, so switching browsers isn't a solution. The
sooner you can get this problem resolved the better it will be for me and
my business.
Issue 122915 has been merged into this issue.
I don't have any web fonts, per se, installed locally, but I do have
Adobe's Myriad Pro family installed (OpenType OTF fonts). When I deactivate
them, Chrome displays just fine.
Comment #74 on issue 108645 by bugdro...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645#c74
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=131699
------------------------------------------------------------------------
r131699 | ba...@chromium.org | Tue Apr 10 19:31:02 PDT 2012
Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/renderer/renderer_webkitplatformsupport_impl.cc?r1=131699&r2=131698&pathrev=131699
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/common/mac/font_loader.mm?r1=131699&r2=131698&pathrev=131699
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/browser/renderer_host/render_message_filter.cc?r1=131699&r2=131698&pathrev=131699
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/browser/renderer_host/render_message_filter.h?r1=131699&r2=131698&pathrev=131699
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/common/mac/font_loader.h?r1=131699&r2=131698&pathrev=131699
M
http://src.chromium.org/viewvc/chrome/branches/1084/src/content/common/sandbox_mac_fontloading_unittest.mm?r1=131699&r2=131698&pathrev=131699
Merge 131324 - Mac: OOP font loading should run on FILE thread.
FontLoader calls file_util::GetFileSize() and file_util::ReadFile(),
which should be called from the file thread, but FontLoader runs on the
io thread now. Make it run on the file thread.
BUG=108645
TEST=none
Review URL: http://codereview.chromium.org/9950141
TBR=ba...@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10052006
------------------------------------------------------------------------
actually worst update I've experienced. Hate to switch to other browsers
just to read some text.
when is this going to be fixed and pushed as update?
I'm using foxfire for my banking now [hopefully a temporary situation]. See
attached Chrome screenshot.
Attachments:
Banking Screenshot 2012-04-11 at 10.03.47 AM.png 55.3 KB
Sorry, Firefox
Running Chrome 18.0.1025.151 on my Mac Pro with Font Agent Pro. I have to
switch to Safari now. Firefox is interminably slow, and this bug has made
Chrome completely unusable. I can't read anything on any site, my gmail
content, etc. Please notify me if it's ever fixed. Or is there is any way
to revert to a previous version of Chrome that didn't have this problem?
Thanks!
Attachments:
Screen Shot 2012-04-11 at 2.10.20 PM.png 395 KB
Mstone-19, does that mean we have to wait for 19?
This bug has been around since weeks.. yet, nothing happens...
Are you forcing us to switch to firefox or safari? seriously?
Yeah. Is quite annoying to work under such conditions in the browser. For
those looking for a temporary "fix" / workaround, deactivating locally
installed fonts in FontExplorer and I suppose any other font management
software helps. At least does for me.
The bug seems to be related to locally activated fonts only.
Issue 123146 has been merged into this issue.
Comment #89 on issue 108645 by ba...@chromium.org: "font-family": Local
font shows odd symbols/characters
http://code.google.com/p/chromium/issues/detail?id=108645
I'd like to close the bug as Fixed, given the fix landed trunk and M19
branch. I'm not in a position to decide whether we should merge the patch
to the current stable channel.
I don't understand how this could possibly be marked as "fixed". I'm sure
there's some technical reason you're marking it as such because you found a
fix, but it's not fixed. I'm in Chrome right now, on StackOverflow, and
all the code is still showing up as glyphs. I'm not interested in trunks
and branches, I'm interested in the Chrome that I have installed, which is
set to auto-update itself. Please do not marked this as FIXED until it is
actually fixed AND PUSHED to the masses.
That's how software development works. The bug is fixed. Getting it built
and pushed in another issue. Marking the bug as fixed is correct.
Maybe I missed something in the thread, but it seems like a workaround has
been found. The bug is not fixed. Right? It's like saying my car is fixed
because I can jump-start it; it's still not operating properly.
Does it just mean the solution has been found but not yet implemented?
I was reading and sent here for this issue from google groups. the
suggestion was to download museo sans. I went there and it is a page that
when clicked for download takes you to a sales page; where the font is
134.00. I think that is a bit of a scam. Here's the link... Don't get
tricked into buying. http://www.fontspring.com/fonts/exljbris/museo-sans
"Maybe I missed something in the thread, but it seems like a workaround has
been found. The bug is not fixed. Right? It's like saying my car is fixed
because I can jump-start it; it's still not operating properly."
This. One million times this.
I understand what you're saying about "this is how software development
works", but I disagree. Until the fix is in the hands of the users, it is
not really fixed. It is identified, and under active development, but it
is not truly fixed until there is a release. When a client sends a bug
over and I fix it locally, I don't tell them it's fixed until we release
said fix to them. That's how software development works to me.
My igoogle page has returned to normal. Here's a page from an online news
org...still exhibiting the font problem. My own web page [efsmart.com] is
still a mess.
Attachments:
Screen shot 2012-04-12 at 11.06.31 AM.png 360 KB
You'll have to accept apologies from those of us who post redundant screen
shots and issues. We don't mean to be bothersome. We don't understand fully
how you handle these sort of things, and often find your notes difficult to
follow. We speak from the viewpoint of being ordinary non-tech people who
assumed that developers want to see what we are seeing, and that somehow we
would fresh our browsers each morning and all this would be worked out.
Any real solution to this F++n problem??!!
come on..
Are older releases of chrome available for download? I'd like a better
workaround than 'switch to another browser'. I'll direct my customers to it
if they contact us about this issue.
Also, can Google's support or marketing team put out a public statement
about this bug? I run the support department for a font management
developer. We've gotten some heat over this issue, so it would be nice to
have something official to direct our customer base to.
Issue 123226 has been merged into this issue.
what's the timing on this fix?
i've been swithing back and forth to other browsers and would like to know
if we're talking a day or a month?
C'mon google devs! Can someone please just say: "we hope to have this issue
fixed in X days/weeks"? I'll just stop using Chrome altogether if this is
the way you treat major bugs...
Sincerely,
John
Seeing this issue on OS X 10.6.8, Chrome 18.0.1025.162. I'm not using any
font management software.
Attachments:
Chrome_Font_Problem.gif 26.4 KB
google actually pushed an update few days ago I believe. But no changes
about this issue.
Still switching between two browsers.
Are any of you using the Beta channel? We believe this issue was fixed on
the Beta channel on Friday with version 19.0.1084.24. We'd love to have
some feedback so we can make sure we push the fix to the Stable channel too.
where to get it?
@comment113, beta channel is available here:
http://www.google.com/landing/chrome/beta/
Re: Comment 112 by kar...
I commented way back on April 6, 2012 (Comment 56) that the fix landed and
works in Canary <http://tools.google.com/dlpage/chromesxs>.
I also asked a few questions along with that report. None of which were
really addressed. Even as everyone else started asking the same ones.
a.
ok, got the beta installed and seems to be working fine.
Beta working for me as well. Thanks for the fix!
Attachments:
Screen shot 2012-04-15 at 10.47.09 AM.png 178 KB
Fix seems to be working for me. Thanks.
No, it wasn't fixed in version 18. I was running that one up until this
morning and it never worked for me with any regularity. I had switched to
Safari because I do have to read the text on web pages. ;) I use Font Agent
Pro on a Mac Pro.
However, I've switched to the beta version of Chrome (Version 19.0.1084.24
beta) and it appears to be fixed there. Thank you!
.163 is not released yet. The note is from our QA team testing it :)
Thank you for confirming the fix in the Beta channel.
Oops! I'm sorry, I think I spoke too soon. I do still have a problem with
google calendar for some reason. See screenshot (the dropdown menu to
choose my calendar). I cleared my cache and refreshed before taking in this
in case that makes any difference... Looks like other sites that were all
in gibberish (including my gmail) are working though...
Attachments:
Screen Shot 2012-04-16 at 11.46.42 AM.png 144 KB
Verified that the issue is resolved in 18.0.1025.163 & 19.0.1084.24
OS tested: Mac 10.7.2
It looks fine for me with the 18.0.1025.163 (Official Build 132135) on Mac
10.7.3 with calendar app also.
jeremy: I am not having the problem, but was referring to Comment 122.
shushude...: As per comment 128: Please file a separate bug with as much
detail as possible.
just pushed stable channel for mac:
http://googlechromereleases.blogspot.com/2012/04/stable-channel-update_16.html
hopefully 18.0.1025.163 should fix this problem. thank you for your
patience.
I'm running Version 19.0.1084.24 beta; still patches of convoluted fonts,
although not as bad as before. Am I using the wrong version?
If anyone is still having issues then please file a new bug and post the
bug number here. Otherwise, if it's working for you, no need to post here.
Thanks!
OS X 10.6.8, 18.0.1025.163 - issue NOT resolved
Again, please file a *new* bug with as much detail as possible and post the
bug number here - a detailed bug report will help us find the root cause of
the issue.
Why should we bother to post a new bug (which I don't even know how to do
nor do I care to learn) if it is the same bug as this one?