The only thing I can think of is that the CSS file is pointing to the WOFF/OTF etc. files and they are not there, so the browser is falling back to what it knows.
In the case of Firefox and Chrome, they are falling back to the fonts on your system. In the case of Safari, it’s being much more strict and because it can’t find the file, it falls back to Times. This is actually more useful as you know there may be a problem with referencing the actual font files.
In safari, open the broken page. Right click somewhere and choose Show Page Source. The window will gain an inspector at the bottom. At the top, you may see a small red octagon with a number inside. That is telling you that there are page errors. Click on that and see if there are any 404 errors relating to font files (.woff, .otf etc.). Remember, references to these files in the CSS file will be relative to the CSS file, NOT the parent HTML file.
It will help immensely if you can put the problem site somewhere online where we can see the problem in action. Right now, the best we can do is guess what could be going wrong.
freewaytalk mailing list
email@hidden
Update your subscriptions at: