Interesting!
Topics pages on WhippleHill (our Learning Management System) are secure pages, behind a password. You can embed some third-party content on a Topic page behind a password by simply pasting in the embed code and there you go... like youtube and Google Forms.
Other sources of embed code need to be tweaked to trick the browser into thinking it is coming in as a secure source, and here is how you trick it:
Where you see the web address, add an s to the http so it is now https. This works for Padlet, Prezi, and hopefully others. But not TED.com (you'll have to link to them for now instead of playing them on the page).
Remember to change the width to 100% so it fills the space correctly and not too wide.
Example:
From testing I see that Safari seems to display things on a secure page without complaining. So if you use Safari exclusively you may be unaware of this issue.
Internet Explorer may ask permission and then work fine. FireFox and Chrome do not ask, and will not display the non-secure code on a secure page. There may be settings that I'm not aware of, but you can't' assume everyone knows how to change settings like this on the fly. Especially teachers and students. So tweak the embed code to be on the safe side.
Topics pages on WhippleHill (our Learning Management System) are secure pages, behind a password. You can embed some third-party content on a Topic page behind a password by simply pasting in the embed code and there you go... like youtube and Google Forms.
Other sources of embed code need to be tweaked to trick the browser into thinking it is coming in as a secure source, and here is how you trick it:
Where you see the web address, add an s to the http so it is now https. This works for Padlet, Prezi, and hopefully others. But not TED.com (you'll have to link to them for now instead of playing them on the page).
Remember to change the width to 100% so it fills the space correctly and not too wide.
Example:
From testing I see that Safari seems to display things on a secure page without complaining. So if you use Safari exclusively you may be unaware of this issue.
Internet Explorer may ask permission and then work fine. FireFox and Chrome do not ask, and will not display the non-secure code on a secure page. There may be settings that I'm not aware of, but you can't' assume everyone knows how to change settings like this on the fly. Especially teachers and students. So tweak the embed code to be on the safe side.
I wonder if there is some way in which our browsers can automatically detect this issue and insert the "s" to save us the time from having to manually input it for some websites.
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDelete