Opened 14 years ago
Closed 14 years ago
#21399 closed defect (bug) (fixed)
Twenty Twelve: use protocol relative URL to load Google Fonts
| Reported by: | lancewillett | Owned by: | lancewillett |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.5 |
| Component: | Bundled Theme | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Description
To avoid insecure content errors in Theme Customizer we should use relative protocol URL in the font CSS enqueue call.
Attachments (3)
Change History (7)
#3
@
14 years ago
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.
Version 0, edited 14 years ago by
(next)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Won't this mess with back-compat? It was only introduced in [21166].