delete-peyman / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Droid Sans / Droid Serif not working in Google Chrome - OS X #42

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. View the font directory
2. View Droid Sans / Droid Serif

What is the expected output? What do you see instead?

I'd expect to see the font working properly. It doesn't. It shows some weird 
font that looks like TImes New Roman.

What version of the product are you using? On what operating system?

Google Chrome OS X version 9.0.597.102

Original issue reported on code.google.com by subim...@gmail.com on 17 Feb 2011 at 7:21

Attachments:

GoogleCodeExporter commented 9 years ago
Unable to reproduce, but I think there's a real issue, as others have reported 
similar results. Can you use "Inspect Element" and post screenshots of the 
network requests? Clicking through to the family will help keep the traffic 
clean, as opposed to reporting on the top-level directory page.

Original comment by r...@google.com on 23 Feb 2011 at 1:24

GoogleCodeExporter commented 9 years ago
I am having the same issues on my machine.
Google Chrome OS X version 9.0.597.102
Mac OS x 10.6.6

Original comment by tbob...@gmail.com on 23 Feb 2011 at 3:38

Attachments:

GoogleCodeExporter commented 9 years ago
These are the screenshots of the network requests:

Original comment by tbob...@gmail.com on 23 Feb 2011 at 3:44

Attachments:

GoogleCodeExporter commented 9 years ago
I'm on OS X 10.6.6 and Chrome 10.0.648.127. I use FontExplorer X to manage my 
fonts. I disabled Droid Serif from my fonts and still had the problem. I then 
disabled Droid Sans from my fonts and the problem went away. So there seems to 
be a conflict with me having Droid Sans installed locally.

Original comment by cku...@gmail.com on 23 Mar 2011 at 5:15

GoogleCodeExporter commented 9 years ago
Exact same problem here. Also on FontExplorer X for font management.

Original comment by Dan.Te...@gmail.com on 17 Apr 2011 at 8:18

GoogleCodeExporter commented 9 years ago
Disabling Droid Serif locally in FontExplorer X removed the problem for me as 
well.

Original comment by m...@tylerpaulson.com on 17 Apr 2011 at 8:36

GoogleCodeExporter commented 9 years ago
I am also able to repeat this conflict over and over. Disabling the local font 
files fixes the problem, which only exists in Chrome. It also doesn't seem to 
be an issue with different font file managers as it conflicts with Chrome no 
matter which manager is used.

Original comment by hehnd...@gmail.com on 10 May 2011 at 7:09

GoogleCodeExporter commented 9 years ago
I'm also experiencing the exact same issue -- when Droid Sans is enabled 
locally, the font doesn't work in Chrome, defaulting to a serif font. Disabling 
the font locally makes it work again.

Original comment by aaron.hildebrandt on 22 Jul 2011 at 12:26

GoogleCodeExporter commented 9 years ago
Having the same problem with droid sans not appearing currently in chrome 
browser for the Mac. I do have FontExplorer X installed and the droid sans font 
active on my system. When the droid sans font is not active and I restart 
chrome, the font appears correct in browser. 

Another note is that when I switch to using a different browser such as Safari, 
font appears correct regardless of being active in FontExplorer X.

Original comment by mwc1...@gmail.com on 10 Aug 2011 at 1:33

GoogleCodeExporter commented 9 years ago
Works on all browsers i have tried on Windows and Linux but looks like a 
standard serif font on my iPad.

Original comment by rafesacks on 17 Oct 2011 at 4:53

GoogleCodeExporter commented 9 years ago
Same issue here. Disabling the font solved the problem, but it's problematic as 
I'd like to enable the font occasionally for design work. Bump!

Original comment by marshall...@gmail.com on 23 Oct 2011 at 9:56

GoogleCodeExporter commented 9 years ago
I can confirm the problem as well. OS X 10.6.7, Chrome 15.0.874.120.

Original comment by nextcomt...@gmail.com on 16 Nov 2011 at 2:30

GoogleCodeExporter commented 9 years ago
I'm having this problem with Open Sans using Windows XP.  Issue exists in FF7, 
FF 8.0.1, and FF beta 9.  Problem is only on a machine that has the font 
installed locally.

Original comment by kristinl...@gmail.com on 13 Dec 2011 at 5:43

GoogleCodeExporter commented 9 years ago
I'm sorry about this Chrome bug, but its not something I or the Web Fonts team 
can help with directly. Please find the relevant bug in the Chromium issue 
tracker and report your concerns there :-)

Original comment by dcrossland@google.com on 13 Dec 2011 at 5:53