It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I have the problem, that my browser (chrome) on Mac OSX (10.11.2) refuses to load some fonts.

Here is the log from the console:

Font from origin 'http://fonts.gstatic.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.gog.com' is therefore not allowed access.
avatar
geckoman: I have the problem, that my browser (chrome) on Mac OSX (10.11.2) refuses to load some fonts.

Here is the log from the console:

Font from origin 'http://fonts.gstatic.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.gog.com' is therefore not allowed access.
 
Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the resource originated.

Something seems to be interfering on your side.  Google Fonts (fonts.gstatic.com) are served with the Access-Control-Allow-Origin:* header, and Chrome can only render these fonts if the header is left intact.  Some proxies can strip the response header, preventing Chrome from rendering the fonts.  If you're <span class="bold">behind a proxy</span>, this <span class="bold">extension</span> might be helpful.  It bypasses the security by changing the response headers when the extension is turned on.  Keep in mind that it also lowers your browser security at the same time.

Before playing with this extension, I highly suggest you to <span class="bold">reset your Chrome settings</span> first.  An update of Chrome could have messed up the settings.  In this case, a browser reset might be the answer.  You could also check with Safari or a different browser, to see if the problem only occurs with Chrome.
 
Post edited January 17, 2016 by _Slaugh_