This isn't really bug, but i think this can be used more effectively.
In demo is in peaflow css:
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 300;
src: local('Open Sans Light'), local('OpenSans-Light'), url(https://fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTfk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
}
Of course all is ok, but i think this can be better:
url(//fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTfk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
The fonts are accessible using HTTPS and HTTP also, in this case will be css filled with correct protocol from webpage.
I'm not expert of google webfonts and i don't know what type of servers they use.
But logically, when the page is HTTP the fonts should be HTTP also (few exceptions).
In demo is in peaflow css:
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 300;
src: local('Open Sans Light'), local('OpenSans-Light'), url(https://fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTfk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
}
Of course all is ok, but i think this can be better:
url(//fonts.gstatic.com/s/opensans/v10/DXI1ORHCpsQm3Vp6mXoaTfk_vArhqVIZ0nv9q090hN8.woff2) format('woff2');
The fonts are accessible using HTTPS and HTTP also, in this case will be css filled with correct protocol from webpage.
I'm not expert of google webfonts and i don't know what type of servers they use.
But logically, when the page is HTTP the fonts should be HTTP also (few exceptions).