Should not embed GFont, to comply with GDPR

[geek-merlin]

Title: Should not hard embed GFont, to comply with GDPR

In germany we have first GDPR cease-and-desist(-and-pay) letters for GFonts, so they should not be embedded.

Steps

Use and view a page.

Expected Result

Must not embed external assets.

Actual Result

@import url('https://fonts.googleapis.com/css?family=Lato:400,700,400italic,700italic&subset=latin');

Version

current master

Testcase

n/a

[hmaesta]

You can disable loading fonts from Google Fonts by setting @importGoogleFonts: false on your theme's site.variables

For example, on line 16 of default theme.

[geek-merlin]

Thanks!

It looks that you have to do a complete build yourself then?

[hmaesta]

Yes, you have.
That's a easier way of building just the CSS with LESS-only distribution

[j5k]

Or download the css and fonts from google to local and remove the import line from the css file

[jlukic]

I generally use fonts from latofonts.com and skip the import when building custom builds myself.

[kaisbensalah]

Apart from GDPR, and as I pointed out in the issue #6599, importing the fonts via HTTP will affect UI loading performance, and increase latency. The method used for importing google fonts results in extremely annoying behavior. I think this issue needs more attention.

[kaisbensalah]

Why not include the google fonts along with the source code resources, instead of forcing the library to fetch them externally each time when being loaded?