Re: BUG: Google Fonts Can Fail

Posted by Devilin Pixy on Oct 02, 2019; 1:13pm
URL: https://support.nabble.com/BUG-Google-Fonts-Can-Fail-tp7604162p7604306.html

With the move to https for my forum, it appears that no fonts are available at all due to the calls being made to Google Fonts API (Web Fonts) over http. This will result in those calls being blocked (mixed content) as they required to be made over a secure connection (https) as well.

What you end up seeing is the browser default font.

I actually even doubt that Nabble makes use of custom (named) fonts, which should be available on the server itself, with a reference to the location (@font-face). I could have missed it while going through the several sources, but to me it looks like only Google Web Fonts are being used, located in 'GWF\', with the option to choose any other Google Web Font available.

The use of Google Web Fonts is fine, as they are highly compressed and downloaded fast on demand. Then they are stored within the browser, for use elsewhere too. Just too bad they will be blocked when you have switched to https  (mixed content), because calls to them are still using http.

I hope Nabble will fix this soon, which is easy, as there are only a couple of locations where they 'forgot' to change http to https.