Skip to content
This repository has been archived by the owner on Sep 25, 2019. It is now read-only.

Switched to HTTPS to avoid mixed content warning #438

Closed
wants to merge 3 commits into from
Closed

Switched to HTTPS to avoid mixed content warning #438

wants to merge 3 commits into from

Conversation

ZhangYiJiang
Copy link
Contributor

I noticed that Firefox was issuing a mixed content warning on the edutech homepage (which seems to use Coursemology, though I'm not sure how the two codebases are related). I'm not actually sure where Google's JS API is used in Coursemology, but fixing the mixed content warning is simple enough.

As an aside: Using the async attribute for MSIE < 9 is pretty pointless, because IE only started supporting async at v. 10+ - http://caniuse.com/#feat=script-async

@lowjoel
Copy link
Member

lowjoel commented Aug 15, 2015

I would prefer using a protocol-relative URI. Edutech is by a separate team and we do not run it.

Adding an async attribute would probably not change the behaviour for the html5 shim, even if the user-agent does not support the attribute.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants