Twenty Twelve: use protocol relative URL to load Google Fonts

[lancewillett]

To avoid insecure content errors in Theme Customizer we should use relative protocol URL in the font CSS enqueue call.

[obenland]

Won't this mess with back-compat? It was only introduced in [21166].

[lancewillett]

Replying to obenland:

Won't this mess with back-compat? It was only introduced in [21166].

We'd need to test to see how older versions of WP would react. The alternate is to check is_ssl() and output the correct protocol in the path. Which is not as elegant, but works.

@nacin, any thoughts?

[nacin]

Prior to 3.5, // is considered a path-relative URL, and the site URL is prepended. So that's a no-go.

We could consider a version check, and then register // if we're good, and otherwise, checking is_ssl(). Not as elegant as a straight is_ssl() check, but at least sets the expectation that you can now do // with enqueues.

Might complicate the theme more than it should, though. I'm fine with a straight is_ssl() check.

[obenland]

Adds is_ssl() check

[obenland]

Version check with is_ssl() as fallback

[lancewillett]

In [21391]:

Twenty Twelve: use is_ssl() to load the correct protocol for Google font CSS file. Fixes #21399, props obenland.