Google Fonts URL is not https!

Marco
171 Posts
Marco posted this 16 March 2017

PLEASE FIX! THE PROBLEM WITH GOOGLE FONTS LINK! IT´S JUST HTTP BUT SHOULD BE HTTPS!!!

Every Page I create I need to fix this URL from http to https! If I use a secured website the fonts will not shown instead visitors will see just times new roman!!!

PLEASE FIX! THE PROBLEM WITH GOOGLE FONTS LINK! IT´S JUST HTTP BUT SHOULD BE HTTPS!!! Every Page I create I need to fix this URL from http to https! If I use a secured website the fonts will not shown instead visitors will see just times new roman!!!
google-fonts https
Vote to pay developers attention to this features or issue.
29 Comments
Order By: Standard | Newest
Stagger Lee
1818 Posts
Stagger Lee posted this 19 July 2017

No matter what you do, just dont force ME to use https. Make it as optional option if you wish.

No matter what you do, just dont force ME to use https. Make it as optional option if you wish.
Marco
171 Posts
Marco posted this 19 July 2017

you dont understand Stagger. the google fonts NEEDS to be https... also if YOU dont use it and your site ist only http.
Look into sourcecode of any regular website.
the google fonts url starts always and everywhere with https.
YOU can still use http for your website - all will work fine.

BUT:
If YOU are using httpS and Google Fonts URL is only http -> it will not work!
as http on httpS -> OMG*

Noone will force YOU to use httpS :)

you dont understand Stagger. the google fonts NEEDS to be https... also if YOU dont use it and your site ist only http. Look into sourcecode of any regular website. the google fonts url starts always and everywhere with https. YOU can still use http for your website - all will work fine. BUT: If YOU are using httpS and Google Fonts URL is only http -> it will not work! as http on httpS -> OMG* Noone will force YOU to use httpS :)
DaveOzric
935 Posts
DaveOzric posted this 19 July 2017

Most services use https when you add them to your site. Facebook, Google, etc. It only matters if they are not https and you are. Not the other way around like Marco said.

Most services use https when you add them to your site. Facebook, Google, etc. It only matters if they are not https and you are. Not the other way around like Marco said.
thfischbach
29 Posts
thfischbach posted this 19 July 2017

Marco, you only need to change line 19 in index.html of an HTML-Theme. There you can add an "s" to the google url and your problem is solved. Takes about one Minute!

Marco, you only need to change line 19 in index.html of an HTML-Theme. There you can add an "s" to the google url and your problem is solved. Takes about one Minute!
Marco
171 Posts
Marco posted this 19 July 2017

fischbach, why I should do that?
Paying on a subscription base since artisteer 1. So why I should do this manual?

Its a fix which takes 5mins MAX for the themler team!

Tell you something:
I have ~50 html templates which I need to update all few weeks.
Do you know - can you imagine - what work this is, to
a) update all pages in themler and then
b) manually update all pages from http google to httpS google???

Comon...
If I have only 1 html page, okay. But in that case? NO!
I want this f* Bug fixed!

Okay, no. For me it doesnt matter, as I already moved to another Tool like i said yesterday

fischbach, why I should do that? Paying on a subscription base since artisteer 1. So why I should do this manual? Its a fix which takes 5mins MAX for the themler team! Tell you something: I have ~50 html templates which I need to update all few weeks. Do you know - can you imagine - what work this is, to a) update all pages in themler and then b) manually update all pages from http google to httpS google??? Comon... If I have only 1 html page, okay. But in that case? NO! I want this f* Bug fixed! Okay, no. For me it doesnt matter, as I already moved to another Tool like i said yesterday
Marco
171 Posts
Marco posted this 19 July 2017

Außerdem ist es mir zu mühsam in englisch zu schreiben.
Du kannst mich gern via Facebook (marco.vantroba) kontaktieren, da können wir uns gern austauschen.
Mir ist das hier mittlerweile nur noch zu blöd.

Schau mal, wie lange dieser lächerliche Bug besteht. Und da gibt’s noch viiiiele andere ungelöste...

Außerdem ist es mir zu mühsam in englisch zu schreiben. Du kannst mich gern via Facebook (marco.vantroba) kontaktieren, da können wir uns gern austauschen. Mir ist das hier mittlerweile nur noch zu blöd. Schau mal, wie lange dieser lächerliche Bug besteht. Und da gibt’s noch viiiiele andere ungelöste...
Stagger Lee
1818 Posts
Stagger Lee posted this 02 December 2017

I run upon this WP plugin. Simple, few lines of code.

https://wordpress.org/plugins/http-https-remover/

I run upon this WP plugin. Simple, few lines of code. https://wordpress.org/plugins/http-https-remover/
emailrobind
27 Posts
emailrobind posted this 19 September 2018

Yes today is 9/19/2018 and this issue is still not resolved all my stylesheets are giving errors due to this issue. The mixed content error causing my fonts to not render correctly on chrome.

Yes today is 9/19/2018 and this issue is still not resolved all my stylesheets are giving errors due to this issue. The mixed content error causing my fonts to not render correctly on chrome.
emailrobind
27 Posts
emailrobind posted this 19 September 2018

HTML Versions also showing up these errors too

Also throwing up these errors too Intervention: Passive Event Listener for type == "mousewheel" && target == window && function_name == "ssc_wheel"
User input
The smoothscroll.js code is largely broken and is preventing us from shipping scroll top interop. With the scroll top interop behavior activated sites fail to scroll at all with the wheel event. This library was corrected a few years ago but the web continues to clone the broken version and we have been blocked in shipping this long implemented fix for interop.

Smooth scroll has been enabled in Chrome for a number of releases so using custom smooth scrolling is not necessary anymore.

Documentation
https://docs.google.com/document/d/1yMAUU0wCeP7BIlQujqfwe3LBnG0QJaqymbkZwor9u60/edit#
Status in Chromium
Blink components: Blink>Scroll

Enabled by default (tracking bug) in:

Chrome for desktop release 61
Chrome for Android release 61
Android WebView release 61
Opera release 48
Opera for Android release 48
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Firefox:
No public signals
Edge:
No public signals
Safari:
No public signals
Web Developers:
No signals

HTML Versions also showing up these errors too Also throwing up these errors too Intervention: Passive Event Listener for `type == "mousewheel" && target == window && function_name == "ssc_wheel"` User input The smoothscroll.js code is largely broken and is preventing us from shipping scroll top interop. With the scroll top interop behavior activated sites fail to scroll at all with the wheel event. This library was corrected a few years ago but the web continues to clone the broken version and we have been blocked in shipping this long implemented fix for interop. Smooth scroll has been enabled in Chrome for a number of releases so using custom smooth scrolling is not necessary anymore. Documentation https://docs.google.com/document/d/1yMAUU0wCeP7BIlQujqfwe3LBnG0QJaqymbkZwor9u60/edit# Status in Chromium Blink components: Blink>Scroll Enabled by default (tracking bug) in: Chrome for desktop release 61 Chrome for Android release 61 Android WebView release 61 Opera release 48 Opera for Android release 48 Consensus & Standardization After a feature ships in Chrome, the values listed here are not guaranteed to be up to date. Firefox: No public signals Edge: No public signals Safari: No public signals Web Developers: No signals
You must log in or register to leave comments