Visibility of Embedded content

We have recently received a large number of queries regarding embedded content not displaying for users in some browsers.  This is occurring because of security changes within browsers and is not caused by any changes within itslearning.  The main browsers affected by this are Chrome and Firefox although Internet Explorer has had the same restrictions in place for a long time and prior to IE10 presented this as a pop-up.




The underlying issue behind all this is a change in the stance of browser developers regarding mixed active content.  Mixed content refers to viewing unsecured (http:) content via a secure (https:) page (or secured content on an unsecured page) and 'active' includes anything that adds interactive elements to the page.  In the case of YouTube, this isn't the video itself (which is passive content) but is the video controls that YouTube uses.

As this is an internet wide change the correct solution is for the content provider (i.e. YouTube) to alter their embed code to account for the site it's placed on.  A number of sites that see regular use have already done this:

This means any embed link you take from those sites today will work correctly and should be added by copying the code (please see this article for help) and then clicking the 'source' button in the text editor and pasting the contents in full. (The insert > web 2.0 content option should be used with care currently as it will allow you to add an embed that will not display)

Content previously embedded from these sites may not display, if this is the case you can resolve this manually by following the specific advice for each site in the attached document.

In addition to the sites above that are working correctly without changes there are a number of other sites that will work but require you to alter the code provided, the sites below have all been tested and confirmed as working with adjustments, an example of each is provided on the attached document.
Animoto is a special case and doesn't support the 'fix' described in the attached document but does allow you to tailor your embed code when it's created.  The key being that you have to tick the 'Use SSL' option.

Any providers not listed either haven't been tested or do not currently support https:

Have more questions? Submit a request


Powered by Zendesk