It is just a Cross Origin resource sharing issue. This is because technically you are serving the fonts from a different sub domain than the page. This is because you have the path to your fonts with the www in it and you are probably requesting them from http://pomelopress.com/fonttest09.
Obviously you need to account for requests coming from both variants and this is achieved by telling your server to allow the fonts to be accessed from other locations. You do this by adding the following instruction to your htaccess in the directory where the fonts are located:
Header set Access-Control-Allow-Origin "*"
or if you just want to allow certain domains, replace the * with a comma separated list of the domains.
It needs to go at the root of where your fonts are - so in this case the same directory as your published site. public_html or similar.
Have a look via an ftp app and see whether you already have an htaccess file on the server.
If there is already one present you just need to add that line to it and don’t change anything else that way you wont break anything existing.
If there isn’t one, you can either create on in most ftp apps directly or create a text file on your mac called htaccess (NO LEADING DOT - or it will become a system file and invisible). Add the access control line from my post above and save it. Upload it to the root directory of your site via an ftp app and once there rename it to include the leading dot so it becomes .htaccess
This is absolutely correct WHEN the fonts and the website are being served from the same domain (and subdomain) - this is why your page works when you go to the full url with the www in it.
As I mentioned in my first reply, expecting http://mySite.... to serve fronts from 'http//www.mySite..... addresses will cause Chrome and Firefox to trigger a cross origin restriction unless the server tells them that this is allowable - just the same is if you were serving fonts from http://fonts.mySite.com which many people do.
You must have a way with txt files, Andrew. Mine didn’t work, but yours did.
So thank you once more.
A small, but niggling question…I am wondering if you have any idea why the bottom of this H1 Nanu font is being cut off. The same thing happened with your late lamented Font Styles. It’s not the end of the world, but I would love it to go away.
The cut off can happen with some very tall and condensed fonts like that. The simple solution is usually just to add a little bottom and/or top padding or margin to the header stack (in the Stacks layout settings at the very top). The more precise and correct method would be to increase the line height for h1’s using the Font Styles stack in Font Pro
All this discussion about domains and sub-domains has been a revelation. I had no idea, as I did not personally set up pomelopress.com with a sub-domain of www. That is the default configuration on LittleOak, an organization (apropos of another recent discussion) that I am less than enamored with.
In any case, I am very curious: is there a logic to that kind of configuration? Do other internet hosts do it differently?