Comment by leephillips | Hacker News Reader

Comment by leephillips | Hacker News Reader

The embed codes seem to be broken. They are like this:

    <iframe src="//embed.gettyimages.com/embed/141707234?et=bk1OGlvTI0avNVbOUXa3ZA&sig=M0SraL8CHtualNed00tTEEcWOi7KfHFE17a3zoUlQBc=" width="508" height="407" frameborder="0" scrolling="no"></iframe>

with no protocol on the source attribute. Maybe this works in some browsers but it failed in Chrome. Adding the missing "http:" fixes it.

EDIT: please ignore this dumb comment but, if you are really interested, read the replies below.

This is a common pattern for embedding scripts, so the browser will use the same protocol as the parent page loading the element (http or https), avoiding issues with embedding insecure content in a secure page. I thought it worked for iframe elements too - but I guess it's not consistently supported? It works for me in Chrome on Win7.

Edit - more info about "Protocol Relative URLs": http://stackoverflow.com/questions/550038/is-it-valid-to-rep...

My bad. I tested it by loading a page from the local filesystem rather than over the network. It works fine as is, of course.

Reply on news.ycombinator.com