Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: YouTube embed: “Unsafe JavaScript attempt to access frame with URL” - messes up font?
| Status | Resolved |
| Add-on / Version | Reel |
| Severity | Critical |
| EE Version |
Bjørn Børresen
Jun 13, 2012Hi Brian,
if you have a look at the console here you’ll see two javascript errors referring to the youtube embed generated by Wyvern Video: http://www.kavakava.no/tango/
See this image: http://i.imgur.com/Vxd6G.jpg
It seems to mess with webfont just next to the embed: http://i.imgur.com/9lOMG.jpg
If I remove the youtube embed the font looks fine.
btw - couldn’t attach images to this bug ticket so there seems to be an issue with this form.
BoldMinded (Brian)
Looks like I’m going to have to revise how the YT embed works. Simply using the iframe won’t work, a little more is involved. I’ll give it a look tonight and see if I can get you something tomorrow.
BoldMinded (Brian)
Bjorn, I found this thread with a comment from a Vimeo staff member. He claims its only the Inspector that is causing the errors b/c it is trying to access the iframe to inspect it, but it can’t b/c its from a different domain. Do the fonts appear correctly if you don’t have Inspector open?
https://vimeo.com/forums/topic:28492
Bjørn Børresen
Hi Brian,
the font issue was reported by my client which I’m pretty sure doesn’t use the inspector. I’m not able to reproduce it on my windows box (although I do get those JS errors of course). I did however test in Safari 5 using crossbrowsertesting.com and was able to reproduce the font issue (w/o having the inspector open).
I was thinking one solution could be to support the old YouTube embed codes (ie. no iframes) but I see those are deprecated now (even though they might still work).
Anyway, I’m leaning towards calling it a Safari browser bug. Found this on Stackoverflow:
“A frame/iframe from an external page cannot, under any circumstances effect the content of the parent document unless they are from the same domain and port number. It is one of the hard rules of browser security.”
http://stackoverflow.com/questions/6346176/youtube-embed-unsafe-javascript-attempt-to-access-frame
BoldMinded (Brian)
Yeah, this is kind of tricky and I’m not 100% sure what the answer is. Remember though, you can build your own embed code by using the {field_name:video_id} var.
BoldMinded (Brian)
I’m closing this b/c I just don’t think there is a clear fix to it. Based on what I’ve seen Chrome and Safari are just extra picky about the notices and they don’t cause any actual issues. Also the notices only show if you have Firebug or Console open, thus most users will never even see the messages.