I'm trying to use custom font for my client live website. The font is working properly in Chrome, Safari, Opera as well as in IE but not working in Firefox.I follow the Manuel solution that works fine but when I see the firefox network log it show that loaded font size is only 0KB. If I directly open the font link it start downloading font with it's original size.
Related
I employed font -webkit-pictograph;
It displays good on chrome and opera browser,
but as for safari,
It return little helpful info when search -webkit-pictograph safari.
Try to clean cache in browser.
If you open the dev console and see what files the browser is pulling from your site, you'll be able to see if it's downloading the font file in Safari.
I can't work out why my Google fonts in an app I'm developing look so much crisper and cleaner in Chrome than they do in Internet Explorer and FireFox. The difference in the body text isn't so dramatic, but it's particularly noticeable in the heading elements (see examples below).
What's even stanger is that the font rendering in Chrome differs between my app and when using the Google Fonts Typecast tool. The rendering in Typecast looks more like the rendering in IE/FireFox than it does in my app (see examples below).
I'm using the Open Sans Google Font with the following CSS reference:
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet" type="text/css">
I'm also using Bootstrap for my app - not sure if that is relevant but it's the only other thing I can think of that could make a difference.
Google Chrome font rendering (headings look crisp and smooth):
Internet Explorer font rendering (headings look almost pixelated and squarish):
Font rendering in Typecast using Chrome (headings look the same as they do in IE)
Any idea why these fonts are rendering so differently?
UPDATE
I downloaded a showcase solution from Typecast and was getting the same results running the demo locally on my machine, in that the fonts were looking un-crisp, but ultra crisp in my app (both in Chrome). So I created a clean .html file with just a h2 heading and a paragraph and added the Google font CSS reference. Ultra crisp. So I started testing on the Typecast show case app which includes the semi bold 600, bold 700 and extra bold 800 fonts. If I remove these fonts and just use the normal 400 the fonts render as crisp and as expected. So that at least explains why I was getting different result in Chrome. But, still I don't understand why other browsers don't render the fonts just as crisply.
I can't seem to find out why this is working for Chrome, but not for Safari.
It should look like this:
But in Safari it looks like the following:
I can see that the font gets loaded, but the computed font (in console) is Sans-serif.
In Chrome it does show the correctly used font family
The problem was with the font files on the server. I had them pulled by git, but they somehow changed (file size was also different).
So when I placed them manually on the server, the font was working properly again.
I have a simple webpage that calls up to external stylesheets, one for google's webfonts, the other to a css file on my own server.
This works fine for desktop tests on IE9, FF, Chrome as well as Android chrome and IOS6 Safari -
but on IOS6 - Chrome no luck.
On chrome even though the webfont stylesheet sheet loads, my own external stylesheet doesn't - does anyone have a clue?
The webpage my webpage
My stylesheet my stylesheet
For a site we're developing we've been using Lato from Google's WebFonts API. It works perfectly in every browser (even IE), except for one very important case: Firefox 3.6 on Windows XP (haven't tested in Win 7 yet). The font loads and is displayed, but the characters look awful, like antialiasing completely malfunctioned.
My googling has found hits about problems with webfonts in FF4 due to a bug in the browser, but I can't find anything about 3.6. Is there something we can do to fix this?
The reason Google's font looks like that has to do with a setting in the font's GASP table. This table toggles 'grayscale' and 'gridfitting' for ranges of sizes. I looked at the font Google is sending to your site and for sizes 0-13 grayscale is turned on. 14-18 is set for gridfitting, which results in black and white rendering. Then 19+ is set for both grayscale and gridfitting. I bet if you changed the size of the text to 13px, it would suddenly turn antialiased.
As for Font Squirrel fonts, we set the GASP table to render grayscale+gridfitting for all sizes above 4px.
There seems to be a difference between Google webfonts and the same font downloaded from Font Squirrel, see this (unrelated...) question.
So I would try and use the version they have at Font Squirrel to see if that solves the problem.