33

I'm working on making my site look the same under Safari and Chrome. In Chrome it looks exactly how I want it to. The major problem is that Google Font doesn't seem to be loading under Safari. Because I'm using the exact code given on the Google Font site, I can't understand why Safari won't fetch it. Is it just incompatible with Safari and I have to rely on a fallback font?

The site can be found here

Juicy
  • 11,840
  • 35
  • 123
  • 212
  • 1
    For the nav, you have an empty `ul` tag in the menu. – Nick R Jun 05 '14 at 13:45
  • @NickR +1 Thanks, actually it was supposed to be the ending tag. – Juicy Jun 05 '14 at 13:49
  • 1
    Ah it turns out that it is actually working. But you have `font-weight:bold` on the `
      ` tag, which is causing the font to look so different in Chrome vs Safari - if you have a look at this image of the site in Safari with font-weight:bold turned off : http://i.imgur.com/tBvw25F.png Basically don't use the `light` version of the font and try and make it bold in `CSS`, instead use the `bold 700` version of the font - http://www.google.com/fonts#UsePlace:use/Collection:Nunito
    – Nick R Jun 05 '14 at 14:13
  • @NickR Thank you! It does look better now. I've taken the bold weight off, it's closer to what I want it to look like. Is it normal that fonts with exactly same config look different between browsers? Or does it stem from my poor CSS skills? – Juicy Jun 05 '14 at 14:16
  • I think this article explains it quite nicely - http://alistapart.com/article/say-no-to-faux-bold – Nick R Jun 05 '14 at 14:30

11 Answers11

40

Your CSS should not only contain

font-family: 'Source Sans Pro', sans-serif;

it should also have values for FONT-STYLE and FONT-WEIGHT:

font-family: 'Source Sans Pro', sans-serif; 
font-weight: 900; 
font-style: italic;

in case you use a font that contains those values like for example: https://fonts.googleapis.com/css?family=Source+Sans+Pro:900italic

Raphaël Balet
  • 6,334
  • 6
  • 41
  • 78
Robert
  • 451
  • 4
  • 4
  • 1
    Yes adding `font-style` and `font-weight` worked for me. I was using an italic version of a font imported into a sass file, it worked on Chrome, but needed the `font-style` and weight for safari – timhc22 Jun 02 '16 at 09:48
  • Holy crap I've spent hours today trying to figure out why a custom font wouldn't load on MacOS/iOS - font-weight and font-style were already declared in the @font-face declaration but finally adding this to the main CSS declaration where the font is defined finally made it load correctly on Safari. Thanks for saving me from bashing my head against the wall! – Charlie Feb 07 '23 at 18:35
17

A 2018 update

I've had this problem in the past and I've had to resort to the option of providing more font file formats. I was a bit surprised to encounter it again in 2018. But it turned out that my problem was not with file-formats but simply with not requesting and specifying the correct font weights.

If we don't customize the URL for requesting this font from Google our link tag will look like this:

<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro" rel="stylesheet">

Let's have a look at what is inside that requested URL. It's going to contain several font-face rules looking something like this:

/* latin */
@font-face {
  font-family: 'Source Sans Pro';
  font-style: normal;
  font-weight: 400;
  src: local('Source Sans Pro Regular'), local('SourceSansPro-Regular'), url(https://fonts.gstatic.com/s/sourcesanspro/v11/6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7l.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

Notice the font-weight attribute. It's specified as 400 which is a "normal" weighted font. Some browsers are able to take this font and turn it into a bold and still look half way decent. This is called "faux bold". It's never going to look as good as a hand crafted bold font though. And on some browsers, notably mobile Safari, it's going to fall down flat and look horrible.

The remedy is to request and specify the actual font weight variants you want to use. In my case it looks like this:

Screenshot from Google Web Fonts

This will produce the following link tag:

<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700&amp;subset=latin-ext" rel="stylesheet">

If you look at the contents of that URL you'll find that there are now entries for font-face rules font-weight: 700 in there.

Now if I want to use the bold version of this font for my h1 tags I'll use the following CSS.

h1 {
    font-family: 'Source Sans Pro', sans-serif;
    font-weight: 700;
}

Most browsers will automatically set h1 as font-weight: bold. If I want to take advantage of that default setting I have to provide my own font-face rules. I can do this by simply duplicating the font-face rules supplied by Google, exchaging font-face: 700 for font-face: bold and putting those changed rules in my own css.

So this rule:

/* latin */
@font-face {
  font-family: 'Source Sans Pro';
  font-style: normal;
  font-weight: 700;
  src: local('Source Sans Pro Bold'), local('SourceSansPro-Bold'), url(https://fonts.gstatic.com/s/sourcesanspro/v11/6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

Would become this:

/* latin */
@font-face {
  font-family: 'Source Sans Pro';
  font-style: normal;
  font-weight: bold;
  src: local('Source Sans Pro Bold'), local('SourceSansPro-Bold'), url(https://fonts.gstatic.com/s/sourcesanspro/v11/6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

Now an h1 tags with font-family: 'Source Sans Pro' will be using the correct font variant. If you want a more in depth read check out this 2012 A List Apart article.

oivvio
  • 3,026
  • 1
  • 34
  • 41
  • I don't know why, but my link doesn't work ``, but if I copy the CSS, then it works well. – nZeus Jan 26 '22 at 13:08
13

If you are using an @import code in the css like this

enter image description here

delete it and use link in head tag

enter image description here

Hakan
  • 1,199
  • 1
  • 14
  • 18
10

For some odd reason I have experience this on some web fonts from Google...when this has happened I usually get them to my server and/or convert them in fontsquirrel....Safari should be able to take TTF Files no matter what ver:

Nunito TTF ver

Riskbreaker
  • 4,621
  • 1
  • 23
  • 31
  • 1
    Google Fonts generally work in Safari, so something else must be happening... what version of Safari? How do you know it's not working -- are you seeing an error in your dev tools console? (For how it's used in your nav header, the characters look almost indistinguishable from most sans serif fonts anyway). – Ben Jun 05 '14 at 13:58
  • @BenPoole agreen with Ben ...maybe you can screenshot your Safari and see how it looks? – Riskbreaker Jun 05 '14 at 14:01
  • Just doing a bit of investigating...It's being served up as a `.woff` file - http://fonts.googleapis.com/css?family=Nunito:300 - This says http://caniuse.com/woff that Safari 5.1+ can use `.woff` files, although I just checked OPs site in 5.1.7 (Windows Safari) and the font isn't working. – Nick R Jun 05 '14 at 14:02
8

My case was that I used font name without quotes. So just change

body{
    font-family: roboto, Arial, sans-serif;
}

to

body{
    font-family: 'roboto', Arial, sans-serif;
}

Chrome works perfectly without quotes, but Safari doesn't.

shukshin.ivan
  • 11,075
  • 4
  • 53
  • 69
6

I had a case where a Google Webfont (Londrina) did not show up in Safari (for Windows), because I used text-rendering: optimizeLegibility;. After removing that, it was fine.

Example: http://codepen.io/julia-r/pen/gagbdy

user2622348
  • 145
  • 3
  • 7
4

Twas happening in 2021 for me. Had to switch the ampersand in the URL to &amp;.

<link href="https://fonts.googleapis.com/css2?family=Roboto+Slab:wght@300;700&amp;display=swap" rel="stylesheet">

Steve Chab
  • 319
  • 3
  • 9
0

The only way that solved this problem for me was by updating the link in the head from this:

<link href="https://fonts.googleapis.com/........" rel="stylesheet">

...to this:

<link href="https://fonts.googleapis.com/........" rel="stylesheet" type="text/css" />

My solution was adding the type attribute with a value of text/css to the link element in the head of the file.

Hope that helps someone.

Alicia Sykes
  • 5,997
  • 7
  • 36
  • 64
0

Also we need to pay attention to CSP if we have it configured. In Firefox and Chrome Content Security Policy was asking for font-src but Safari (both macbook and ios) was asking for style-src. Based on your personal policy for fonts, these settings must be adapted per browser as well.

0

today i had a similar problem. Page in Safari (in chrome, firefox, edge all work fine). Problem has been solved.

In order for the font to display in safari, we need to change the font link:

<link href="https://fonts.googleapis.com/css?family=Montserrat:thin,extra-light,light,100,200,300,400,500,600,700,800" rel="stylesheet">

to this:

<link href="https://fonts.googleapis.com/css?family=Montserrat:thin,extra-light,light,100,200,300,400,500,600,700,800&display=swap" rel="stylesheet">

we nedd to add "&display=swap" in the end of the link.

the rest of the css code looks like this:

html, body {font-family: 'Montserrat', sans-serif; font-size: 20px; font-weight: 300; font-style:normal;}
0

I was having the same issue and mine was fixed by adding 2 after css in the URL.

BEFORE

https://fonts.googleapis.com/css?family=Chivo:wght@400;500;600;700&amp;display=swap

AFTERWARDS

https://fonts.googleapis.com/css2?family=Chivo:wght@400;500;600;700&amp;display=swap
Dominic
  • 351
  • 4
  • 18